From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp0.migadu.com ([2001:41d0:303:e16b::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms8.migadu.com with LMTPS id iGQkF18c2mVRPwEAqHPOHw:P1 (envelope-from ) for ; Sat, 24 Feb 2024 17:42:07 +0100 Received: from aspmx1.migadu.com ([2001:41d0:303:e16b::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp0.migadu.com with LMTPS id iGQkF18c2mVRPwEAqHPOHw (envelope-from ) for ; Sat, 24 Feb 2024 17:42:07 +0100 X-Envelope-To: larch@yhetil.org Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=gnu.org header.s=fencepost-gnu-org header.b="TAds/h4H"; dmarc=pass (policy=none) header.from=gnu.org; spf=pass (aspmx1.migadu.com: domain of "guix-devel-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="guix-devel-bounces+larch=yhetil.org@gnu.org" ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1708792927; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:list-id:list-help: list-unsubscribe:list-subscribe:list-post:dkim-signature; bh=QbjcNG16z7ZgJcDbQLEbpF2g+RE5RAilhpZ5P+Rl3Lc=; b=oS5dcCo+HbZJezNthNd42J0GFn1VxuVbr+qCeYdaS2l+ycovVM+c3xw7aab/NU6ZAl2IxU B6G3SUd1zJkYpgCZwkZfjls/Z934kKbriyoVtbChul54kIR4cxIsC1MG/v8rqn9E1XRDz9 1pBlmoO8zYpUl96OvF+xq6mng00voi1Crs4FnnLpOjVPSO48yE+Vqr6sb0ZNYlaMO6QLgg rhoPbcKIxzAIp0pJcDE0+gOFZrUzRg15K7gh+AllqTtA2OQWcaHalm8K0avv1p8O9QJ+Zo AxI2N+wKyLeiunjuOml9p3MTCW8AA3LpXCAnvVqKvJDex8rKxhjHSngqy9ol9A== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=gnu.org header.s=fencepost-gnu-org header.b="TAds/h4H"; dmarc=pass (policy=none) header.from=gnu.org; spf=pass (aspmx1.migadu.com: domain of "guix-devel-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="guix-devel-bounces+larch=yhetil.org@gnu.org" ARC-Seal: i=1; s=key1; d=yhetil.org; t=1708792927; a=rsa-sha256; cv=none; b=j1vmT/6WdtoRhcc3kC++bacIotinHs5TG/InhZaBNScEu9fPvaY039jlK7tmnPZbehzVWt +YEQs3MDIy73tk/A8O52koyhfjz6fLa+0Lb2NplNiOXzeaArKyYJ462ZX80OifK9FygUx4 sC7HRBi+MSY65+YwUjAYeT736c1e/1NCXGsXk9V9MyGDDOIg+f3BkhGccVdli/4nwpb3xk Lx3dPEOfIsnWUDwUSt2HWVok5RSpiz+t9C5r15+az1t6iBzaXJmhwlrcbFs5ZaWquxRa8j D0iwNee9ccCCluI4TZUNtNmG0h0Avmr39zGHYgGNRpUjL8eqxUWJScHKWPcsEg== Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 41E27425B2 for ; Sat, 24 Feb 2024 17:42:07 +0100 (CET) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rdv5o-0005Sc-6N; Sat, 24 Feb 2024 11:41:40 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rdv5m-0005SU-PX for guix-devel@gnu.org; Sat, 24 Feb 2024 11:41:38 -0500 Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rdv5m-0007Q5-7v; Sat, 24 Feb 2024 11:41:38 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=MIME-Version:Date:References:In-Reply-To:Subject:To: From; bh=QbjcNG16z7ZgJcDbQLEbpF2g+RE5RAilhpZ5P+Rl3Lc=; b=TAds/h4Hnohr0jWEuZJM pCpaLr5ioKa6mLJVO37ORNW+KJnfyv0Trh2yVxOZG7zrrcio74vT6CHOLJo6BK3B7qni/yFrVgx6V FbEUELPt8lYI4YcfJrtmyCVqpZg2gZbcDKsW096rF80PU4Lh2+VdcxEF2gQlLzqtaLfsfCEIeDEe9 PjJySqx77sVdo5FDbHOcRiovPCRgYn+NKKl3eJS2112za/cTLZ0dyONLAlrldAybo8r3VAic3n6Mg aNCVGz1fenXtut0RhDs6ioTMkIEqAJ4L8Jy4L7WvJphJGAaazeaLse5EA1SJcdnkI09ctsu2IRIuJ a3vlFeqx6On2YQ==; From: =?utf-8?Q?Ludovic_Court=C3=A8s?= To: Hartmut Goebel Cc: Guix-devel Subject: Re: Using gitlab-ci to maintain a channel? In-Reply-To: <05861375-730e-5933-b3ef-673cabd07475@crazy-compilers.com> (Hartmut Goebel's message of "Fri, 16 Feb 2024 22:28:30 +0100") References: <05861375-730e-5933-b3ef-673cabd07475@crazy-compilers.com> X-URL: http://www.fdn.fr/~lcourtes/ X-Revolutionary-Date: Sextidi 6 =?utf-8?Q?Vent=C3=B4se?= an 232 de la =?utf-8?Q?R=C3=A9volution=2C?= jour de l'Asaret X-PGP-Key-ID: 0x090B11993D9AEBB5 X-PGP-Key: http://www.fdn.fr/~lcourtes/ludovic.asc X-PGP-Fingerprint: 3CE4 6455 8A84 FDC6 9DB4 0CFB 090B 1199 3D9A EBB5 X-OS: x86_64-pc-linux-gnu Date: Sat, 24 Feb 2024 17:41:35 +0100 Message-ID: <877cit7r28.fsf@gnu.org> User-Agent: Gnus/5.13 (Gnus v5.13) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: guix-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+larch=yhetil.org@gnu.org Sender: guix-devel-bounces+larch=yhetil.org@gnu.org X-Migadu-Flow: FLOW_IN X-Migadu-Country: US X-Migadu-Spam-Score: -9.93 X-Spam-Score: -9.93 X-Migadu-Queue-Id: 41E27425B2 X-Migadu-Scanner: mx13.migadu.com X-TUID: c4iAl5puLnkr Hi Hartmut! Hartmut Goebel skribis: > I wonder whether it's possible to maintain a channel using gitlab-ci. Any= thought or experiences to share? [...] > * What version of guix shall be used? Always the latest one? That=E2=80=99s the main conceptual issue: GitLab-CI only knows about the re= po it=E2=80=99s tracking, it doesn=E2=80=99t realize that whether the code the= rein builds fine depends on the =E2=80=98guix=E2=80=99 channel. To get that level of precision, you would need Cuirass, which is what we use at work and for various scientific channels: . Now, GitLab integration is appealing, so it would still be nice to do CI with a fixed revision of Guix, which you would occasionally manually update. It=E2=80=99s a tradeoff. > * The runners need a docker image. Where to I get one? Possibly containin= g a warmed-up cache? (Using a Debian docker image and > installing guix into it on every run sounds like a bad idea.) As I mentioned on help-guix a few days (weeks?) ago, I haven=E2=80=99t foun= d a way to build such an image with Guix, but I=E2=80=99d like to find one! Another option is to use, say, Debian as the base image, and to install Guix on top of it. > * OTOH /gnu/tore could be cached. How much data would this typically be? > * How to clean the cache from unreachable items? > * How to publish the substitutes? I don=E2=80=99t think you could publish substitutes in that setup, unless GitLab-CI offload builds to an actual machine that has =E2=80=98guix publis= h=E2=80=99 running on it. HTH, Ludo=E2=80=99.