[Nix-dev] Zero Hydra Failures (ZHF) project for NixOS
Michael Raskin
7c6f434c at mail.ru
Thu Oct 30 15:10:39 CET 2014
>>> - nixos channel updates only when there are zero failures on jobset (this
>>> would mean reverts will happen often - and I believe that's the correct way
>>> to go instead of blocking people and punishing good testers)
>>
>> Back to the good old times of any failure blocking channel update, m-m-m.
>>
>> But we now have binary cache, so that doesn't matter that much.
>
>I have to say that I am somewhat wary of this approach: not getting a
>channel update because a random package failed seems like an overkill:
>we'll have to wait each time until a privileged person comes on and
>restarts the build and/or wait for a commit causing rebuild. I don't
>think a user will care that a package they'll never use hasn't succeeded.
We have multiple-day latency for channel updates now, I think.
>It'd be cool if it was possible to do ‘given my package list in
>configuration.nix, use the latest commit where all these packages
>succeed’ on NixOS.
In Monotone I would just lobby for creating proper certs. In Git we
would need a branch per NixPkgs attribute, I think.
More information about the nix-dev
mailing list