From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?utf-8?Q?Ludovic_Court=C3=A8s?= Subject: Re: Help wanted: Nightly builds for Guix Date: Sat, 21 Mar 2020 16:55:43 +0100 Message-ID: <87a7491z40.fsf@gnu.org> References: <20200319185048.GA19460@jasmine.lan> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:44449) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jFgTS-0000pR-7N for guix-devel@gnu.org; Sat, 21 Mar 2020 11:55:47 -0400 In-Reply-To: <20200319185048.GA19460@jasmine.lan> (Leo Famulari's message of "Thu, 19 Mar 2020 14:50:48 -0400") 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+gcggd-guix-devel=m.gmane-mx.org@gnu.org Sender: "Guix-devel" To: Leo Famulari Cc: guix-devel@gnu.org, Carl Dong Hello! Leo Famulari skribis: > On Thu, Mar 19, 2020 at 05:29:37PM +0000, Carl Dong wrote: >> I'm wondering where best to start with this. Perhaps it'd be informative= to know >> how regular releases are done and see what's missing there (and perhaps = what >> needs automation)? > > Check the release target in our Makefile. I remember some detailed > descriptions of the entire process from Ludovic in the past, but I can't > remember where to find those messages. The release process is documented at: https://git.savannah.gnu.org/cgit/guix/maintenance.git/tree/doc/release.o= rg As for nightly builds: CI currently builds things like: https://ci.guix.gnu.org/search?query=3Dguix-binary ;binary tarball https://ci.guix.gnu.org/search?query=3Ddisk-image ;ISO9660 image It=E2=80=99s inconvenient to grab, though, for someone who doesn=E2=80=99t = already have Guix. Perhaps we should address that somehow? Thanks, Ludo=E2=80=99.