[Nix-dev] Travis Testing Needs Rethinking

[zimbatm]

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.


On Sat, 13 Feb 2016 at 19:24 Kevin Cox <kevincox at kevincox.ca> wrote:

> On Sat, 2016-02-13 at 17:03 +0000, Adam Russell wrote:
>
> Wouldn't this all be less of an issue if the build on Hydra wasn't behind
> by weeks? Should we talk about how to improve that? Personally I don't even
> know how to navigate or interpret Hydra when I go look at it.
>
>
> I don't think Hydra is actually behind much, the channels are but IIUC
> most builds are actually completing in a couple of hours. (Actually looking
> now I see some 2 day old builds but nothing too terrible
> http://hydra.nixos.org/status).
>
> Getting faster hydra builds might make this less of an issue but there
> will always be a delay. Of course if that delay is very small it won't
> matter much.
>
> _______________________________________________
> nix-dev mailing list
> nix-dev at lists.science.uu.nl
> http://lists.science.uu.nl/mailman/listinfo/nix-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.science.uu.nl/pipermail/nix-dev/attachments/20160214/673823ff/attachment.html