[Nix-dev] Continuous Integration
shea at shealevy.com
shea at shealevy.com
Thu Apr 28 12:37:29 CEST 2016
IMO putting the logic completely into hydra will be too limiting. If
hydra just gives a nix expression some info about the PRs, then the
nix expression can do arbitrary things (e.g. only build PRs from
trusted users, or that don't change stdenv, or whatever). If it's a
jobset tab then you have to add every possible variation into the
hydra UI.
----- Original Message -----
From:
"Domen Kožar" <domen at dev.si>
To:
"Shea Levy" <shea at shealevy.com>
Cc:
"Graham Christensen" <graham at grahamc.com>, "Ericson John"
<john_ericson at brown.edu>, "nix-dev" <nix-dev at lists.science.uu.nl>
Sent:
Thu, 28 Apr 2016 11:32:53 +0100
Subject:
Re: [Nix-dev] Continuous Integration
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 [1]>
wrote:
It can set pull request statuses (e.g.
see https://github.com/shlevy/hydra-github-status-test/pull/3 [2]),
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 [3] 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 [4]>
To:
"Domen Kožar" <domen at dev.si [5]>
Cc:
"Ericson John" <john_ericson at brown.edu [6]>, "nix-dev"
<nix-dev at lists.science.uu.nl [7]>
Sent:
Wed, 27 Apr 2016 18:23:55 -0500
Subject:
Re: [Nix-dev] Continuous Integration
Domen Kožar <domen at dev.si [8]> 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 [9]
http://lists.science.uu.nl/mailman/listinfo/nix-dev [10]
Links:
------
[1] mailto:shea at shealevy.com
[2] https://github.com/shlevy/hydra-github-status-test/pull/3
[3] https://github.com/NixOS/hydra/pull/277
[4] mailto:graham at grahamc.com
[5] mailto:domen at dev.si
[6] mailto:john_ericson at brown.edu
[7] mailto:nix-dev at lists.science.uu.nl
[8] mailto:domen at dev.si
[9] mailto:nix-dev at lists.science.uu.nl
[10] 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/f03bb7a3/attachment.html
More information about the nix-dev
mailing list