GNU bug report logs - #32540
Cuirass: we need a way to manually trigger evaluations

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Clément Lassieur <clement <at> lassieur.org>
Subject: bug#32540: closed (Re: bug#32540: Cuirass: we need a way to
 manually trigger evaluations)
Date: Thu, 25 Mar 2021 13:16:02 +0000

[Message part 1 (text/plain, inline)]

Your bug report

#32540: Cuirass: we need a way to manually trigger evaluations

which was filed against the guix package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to 32540 <at> debbugs.gnu.org.

-- 
32540: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=32540
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Mathieu Othacehe <othacehe <at> gnu.org>
To: Clément Lassieur <clement <at> lassieur.org>
Cc: 32540-done <at> debbugs.gnu.org
Subject: Re: bug#32540: Cuirass: we need a way to manually trigger evaluations
Date: Thu, 25 Mar 2021 14:15:24 +0100

Hello,

> The 'core-updates' and 'staging' branches shouldn't trigger evaluations
> at each commit, because they produce too many derivations.  Instead, the
> admins should have a 'trigger evaluation' button that they use once in a
> while.  That button should be part of an 'admin interface', which should
> be protected by NGINX's 'auth_basic' authentication mechanism.

The admins can now change configure the specifications to build only a
core subset of packages, or all the available packages from the web
interface.

Closing this one,

Thanks,

Mathieu

[Message part 3 (message/rfc822, inline)]

From: Clément Lassieur <clement <at> lassieur.org>
To: bug-guix <at> gnu.org
Subject: Cuirass: we need a way to manually trigger evaluations
Date: Mon, 27 Aug 2018 11:50:21 +0200

The 'core-updates' and 'staging' branches shouldn't trigger evaluations
at each commit, because they produce too many derivations.  Instead, the
admins should have a 'trigger evaluation' button that they use once in a
while.  That button should be part of an 'admin interface', which should
be protected by NGINX's 'auth_basic' authentication mechanism.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.