[Nix-dev] Continuous Integration

[Domen Kožar]

I was talking to Aszlig about this and it would be best if PRs would be a
tab on the jobset. Since jobset defines the inputs, it would be tested for
PRs against that specific branch.

On Thu, Apr 28, 2016 at 11:30 AM, <shea at shealevy.com> wrote:

> It can set pull request statuses (e.g. see
> https://github.com/shlevy/hydra-github-status-test/pull/3), but currently
> you have to manually create the jobset corresponding to the PR and ensure
> that the relevant jobs are captured by the status plugin.
>
> If https://github.com/NixOS/hydra/pull/277 is merged, then there is one
> step left to get automatic PR management: An input plugin which fetches
> information about open PRs on a repo. I'll write it if 277 ever gets in,
> but without 277 or something like it there's no point.
>
>
> ----- Original Message -----
> From:
> "Graham Christensen" <graham at grahamc.com>
>
> To:
> "Domen Kožar" <domen at dev.si>
> Cc:
> "Ericson John" <john_ericson at brown.edu>, "nix-dev" <
> nix-dev at lists.science.uu.nl>
> Sent:
> Wed, 27 Apr 2016 18:23:55 -0500
> Subject:
> Re: [Nix-dev] Continuous Integration
>
>
>
>
>
> Domen Kožar <domen at dev.si> writes:
>
> > It doesn't build PRs, just updates the status.
> >
>
> Does this mean it can build specific branches (master, release-16.04..)
> and set the commit status on those commits? ie: doesn't have anything to
> do with pull request statuses?
>
> Best,
> Graham
> _______________________________________________
> 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/20160428/a6f8897c/attachment.html