vy.com>
>> Cc:
>> "Graham Christensen" <gra...@grahamc.com>, "Ericson John" <
>> john_eric...@brown.edu>, "nix-dev" <nix-dev@lists.science.uu.nl>
>> Sent:
>> Thu, 28 Apr 2016 11:32:53 +0100
>>
>> Subject:
>
ricson John" <
> john_eric...@brown.edu>, "nix-dev" <nix-dev@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
u>, "nix-dev" <nix-dev@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 aga
istensen" <gra...@grahamc.com>
>
> To:
> "Domen Kožar" <do...@dev.si>
> Cc:
> "Ericson John" <john_eric...@brown.edu>, "nix-dev" <
> nix-dev@lists.science.uu.nl>
> Sent:
> Wed, 27 Apr 2016 18:23:55 -0500
> Subject
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
Domen Kožar 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
It doesn't build PRs, just updates the status.
On Wed, Apr 27, 2016 at 9:44 PM, Ericson, John
wrote:
> Support for hydra to build github PR has been added for a few weeks now in
> https://github.com/NixOS/hydra/pull/280 . What's the next step for
> actually using this
Support for hydra to build github PR has been added for a few weeks now in
https://github.com/NixOS/hydra/pull/280 . What's the next step for actually
using this with nixpkgs and hydra.nixos.org?
On Tue, Feb 23, 2016 at 4:46 PM, Ericson, John
wrote:
> > S3 and Hydra PR
> S3 and Hydra PR support
I asked Domen earlier on IRC, but in case anyone else is interested,
is there any way to contribute to these? If this will go most the way
towards continuously updating channel(s) I'll give an arm and a leg.
> IMHO it's very often a fault of some builds or tests failing
IMHO it's very often a fault of some builds or tests failing (sometimes
transiently). Of course, the lag also doesn't help to resolve these
issues quickly, but more people actually fixing that stuff might have
more impact than HW and infrastructural changes.
--Vladimir
smime.p7s
Description:
There are currently on-going improvements to Hydra to upload built packages
to S3 cache instead of central Hydra machine. That should speed up the
bulids a lot. Another thing on horizon are SSDs for the central machine.
That should get evaluation
times down to dozen of minutes instead of hours.
11 matches
Mail list logo