From: zimoun <zimon.toutoune@gmail.com>
To: Marius Bakke <marius@gnu.org>,
Jonathan Brielmaier <jonathan.brielmaier@web.de>,
guix-devel@gnu.org
Subject: Re: Pushed a fix (?) for ACL key location
Date: Sun, 12 Jul 2020 16:21:03 +0200 [thread overview]
Message-ID: <86365wbyr4.fsf@gmail.com> (raw)
In-Reply-To: <87y2noc3qn.fsf@gnu.org>
Dear Marius,
On Sun, 12 Jul 2020 at 14:33, Marius Bakke <marius@gnu.org> wrote:
> One possible solution that has been discussed before is to have the CI
> continously merge master to a 'stable' branch when lights are green.
> There are quite a few challenges to solve with that approach though.
>
> We could make the pre-push hook run 'guix pull' and 'guix system build'
> but it will quickly get annoying. A server-side hook for the same would
> be less annoying, but would have a hard time if someone accidentally
> pushes a full rebuild.
>
> In practice there will always be problems that cannot be caught in an
> automated way. I hope such breakages are rare, but from your message it
> sounds like there were many problems just this week-end?
If all the patches go to Debuggs (guix-patches) then using the commit
(format-patch --base=auto), the infrastructure could automatically
build, run tests, lint etc. then it eases the job of the reviewer and
the substitutes are available when the end-user pull. The merge would
be done by hand --as today-- by the committer (pusher) to master. Well,
Cuirass could track guix-patches instead of tracking master.
The issue of the rebuild-the-world accident could happen. But it could
also happen now, with the current model.
It is a difficult topic but what is the feedback of such initiatives [1,2]?
1: https://patchwork.cbaines.net/project/guix-patches/list/
2: https://data.guix-patches.cbaines.net/
All the best,
simon
next prev parent reply other threads:[~2020-07-12 14:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-12 1:44 Pushed a fix (?) for ACL key location Christopher Lemmer Webber
2020-07-12 11:14 ` Marius Bakke
2020-07-12 11:42 ` Jonathan Brielmaier
2020-07-12 12:33 ` Marius Bakke
2020-07-12 14:21 ` zimoun [this message]
2020-07-12 16:27 ` Jonathan Brielmaier
2020-07-12 13:57 ` zimoun
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86365wbyr4.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=guix-devel@gnu.org \
--cc=jonathan.brielmaier@web.de \
--cc=marius@gnu.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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).