[Nix-dev] Travis Testing Needs Rethinking
Tobias Pflug
tobias.pflug at gmx.net
Tue Mar 1 22:35:11 CET 2016
> On 16 Feb 2016, at 00:06, Александр Цамутали <astsmtl at yandex.ru> wrote:
>
> 14.02.2016, 21:44, "zimbatm" <zimbatm at zimbatm.com>:
>> What if master was always the latest successful hydra build ? People could rebase on top and have cached builds. Nox could also have cached builds.
>>
>> Instead of merging a PR we would instruct Hydra to queue the build. If the build is successful hydra would merge it into master and close the PR. Otherwise it would amend the PR with the build errors. To instruct Hydra we could annotate a PR with a custom message like: "hydra go!".
>>
>> I believe that this would also help to spot regressions faster. Right now Darwin tends to get breaking chances because Nox only tests against Nixos. And since the builds would be done against all OSes we would also be able to merge all the unstable channels.
>
> +1 for passing every change through CI before merging. I don't know about features of Travis CI and if it's possible to implement this with it. But I know that OpenStack Infra uses Zuul for such tasks.
>
>
I still lack insight since I haven't been using nix for that long but this clearly seems like a goal that should be aimed for
More information about the nix-dev
mailing list