From: Andreas Enge <andreas@enge.fr>
To: Mark H Weaver <mhw@netris.org>
Cc: Christopher Baines <mail@cbaines.net>, guix-devel@gnu.org
Subject: Re: Cleaning up branches on savannah
Date: Wed, 12 Jun 2024 11:11:14 +0200 [thread overview]
Message-ID: <ZmlmMorLjWCPealh@jurong> (raw)
In-Reply-To: <87cyon8q61.fsf@netris.org>
Hello Mark,
Am Tue, Jun 11, 2024 at 11:16:59AM -0400 schrieb Mark H Weaver:
> For IceCat updates, which almost always include security fixes, it is
> important to have very fast turnaround time on the test results.
> ci.guix.gnu.org normally starts building the new IceCat within an hour
> or so of the update being pushed to 'gnuzilla-updates', and usually
> finishes the build within 4-5 hours. If, as you say, QA has not been
> keeping up lately, then I'm not sure it will be fast enough for this use
> case.
>
> Also, I'd like to maximize the likelihood that substitutes for IceCat
> updates will be available *immediately* upon pushing them to 'master'.
> That's another motivation for pushing them to a temporary branch that
> ci.guix.gnu.org has been configured to build.
concerning the second paragraph, this will also be the case for going
through QA: It will build the package on the bordeaux build farm, the
substitutes of which are now activated by default on Guix installations.
For the first part, I would still recommend to go with cuirass on berlin,
as it has more build power, and apparently picks up the Icecat build
much faster.
Andreas
next prev parent reply other threads:[~2024-06-12 9:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-07 9:36 Cleaning up branches on savannah Christopher Baines
2024-06-07 12:46 ` Lars-Dominik Braun
2024-06-07 13:43 ` Mark H Weaver
2024-06-07 14:00 ` Christopher Baines
2024-06-11 15:16 ` Mark H Weaver
2024-06-12 9:11 ` Andreas Enge [this message]
2024-06-19 14:00 ` Christopher Baines
2024-06-19 14:03 ` Christopher Baines
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZmlmMorLjWCPealh@jurong \
--to=andreas@enge.fr \
--cc=guix-devel@gnu.org \
--cc=mail@cbaines.net \
--cc=mhw@netris.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.