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

Previous Next

Package: guix;

Reported by: Clément Lassieur <clement <at> lassieur.org>

Date: Mon, 27 Aug 2018 09:54:01 UTC

Severity: normal

Done: Mathieu Othacehe <othacehe <at> gnu.org>

Bug is archived. No further changes may be made.

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 32540 in the body.
You can then email your comments to 32540 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to bug-guix <at> gnu.org:
bug#32540; Package guix. (Mon, 27 Aug 2018 09:54:01 GMT) Full text and rfc822 format available.

Acknowledgement sent to Clément Lassieur <clement <at> lassieur.org>:
New bug report received and forwarded. Copy sent to bug-guix <at> gnu.org. (Mon, 27 Aug 2018 09:54:02 GMT) Full text and rfc822 format available.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

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.




Information forwarded to bug-guix <at> gnu.org:
bug#32540; Package guix. (Mon, 27 Aug 2018 10:18:02 GMT) Full text and rfc822 format available.

Message #8 received at 32540 <at> debbugs.gnu.org (full text, mbox):

From: Gábor Boskovits <boskovits <at> gmail.com>
To: Clément Lassieur <clement <at> lassieur.org>
Cc: 32540 <at> debbugs.gnu.org
Subject: Re: bug#32540: Cuirass: we need a way to manually trigger evaluations
Date: Mon, 27 Aug 2018 12:17:38 +0200
[Message part 1 (text/plain, inline)]
Clément Lassieur <clement <at> lassieur.org> ezt írta (időpont: 2018. aug. 27.,
H, 11:54):

> 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.
>
>
> I agree that we need a mechanism like this. I am not sure about what the
protection
mechanism should be. 'auth_basic' has some appeal, as it is quite easy, but
I would
like to hear some more opinions about that part.
[Message part 2 (text/html, inline)]

Information forwarded to bug-guix <at> gnu.org:
bug#32540; Package guix. (Mon, 27 Aug 2018 12:10:01 GMT) Full text and rfc822 format available.

Message #11 received at 32540 <at> debbugs.gnu.org (full text, mbox):

From: Clément Lassieur <clement <at> lassieur.org>
To: Gábor Boskovits <boskovits <at> gmail.com>
Cc: 32540 <at> debbugs.gnu.org
Subject: Re: bug#32540: Cuirass: we need a way to manually trigger evaluations
Date: Mon, 27 Aug 2018 14:09:07 +0200
Gábor Boskovits <boskovits <at> gmail.com> writes:

> Clément Lassieur <clement <at> lassieur.org> ezt írta (időpont: 2018. aug. 27.,
> H, 11:54):
>
>> 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.
>>
>>
> I agree that we need a mechanism like this. I am not sure about what the
> protection
> mechanism should be. 'auth_basic' has some appeal, as it is quite easy, but
> I would
> like to hear some more opinions about that part.

It's obviously not ideal, and we can implement something more
sophisticated later.




Reply sent to Mathieu Othacehe <othacehe <at> gnu.org>:
You have taken responsibility. (Thu, 25 Mar 2021 13:16:02 GMT) Full text and rfc822 format available.

Notification sent to Clément Lassieur <clement <at> lassieur.org>:
bug acknowledged by developer. (Thu, 25 Mar 2021 13:16:02 GMT) Full text and rfc822 format available.

Message #16 received at 32540-done <at> debbugs.gnu.org (full text, mbox):

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




bug archived. Request was from Debbugs Internal Request <help-debbugs <at> gnu.org> to internal_control <at> debbugs.gnu.org. (Fri, 23 Apr 2021 11:24:09 GMT) Full text and rfc822 format available.

This bug report was last modified 3 years and 4 days ago.

Previous Next


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