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

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

[Clément Lassieur]

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.

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

[Gábor Boskovits]

[-- Attachment #1: Type: text/plain, Size: 692 bytes --]

Clément Lassieur <clement@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.

[-- Attachment #2: Type: text/html, Size: 1037 bytes --]

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

[Clément Lassieur]

Gábor Boskovits <boskovits@gmail.com> writes:

> Clément Lassieur <clement@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.

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

[Mathieu Othacehe]

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