On 16-04-28 07:19pm, Vladimír Čunát wrote:
> Hi.
>
> On 04/28/2016 05:54 PM, Graham Christensen wrote:
> > 1. Is there any promotional material I should pre-print / take with me /
> >whatever to pitch NixOS?
>
> I'm fairly certain we don't have any official stuff like that.
>
> > 3. What is
On Thu, Apr 28, 2016 at 1:45 PM, Vladimír Čunát wrote:
> On 04/28/2016 08:20 PM, Александр Цамутали wrote:
>> Is it possible to apply this approach to binary packages?
>
> I don't think so, but that doesn't seem really relevant. The suggestion
> is to change what our compiler
On 04/28/2016 08:20 PM, Александр Цамутали wrote:
> Is it possible to apply this approach to binary packages?
I don't think so, but that doesn't seem really relevant. The suggestion
is to change what our compiler produces...
--Vladimir
smime.p7s
Description: S/MIME Cryptographic Signature
Is it possible to apply this approach to binary packages?
--
Александр Цамутали
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev
Hello Nixers,
I'll be attendending DevOpsDays Austin this year (May 2nd, 3rd in
Austin, TX) and I suppose I have a few questions.
1. Is there any promotional material I should pre-print / take with me /
whatever to pitch NixOS?
2. Is there anyone else in the community in or near Austin, TX?
i'm not that familiar with node ecosystem, but maybe we should have a
set of node packages per node version like we do with python, ruby,
etc...
On Thu, Apr 28, 2016 at 7:58 AM, Tobias Pflug wrote:
> Hi,
>
> I am looking for some help with my PR which updates libuv to the
That's a good point, but I don't see how a separate tab would contrain
hydra from adding extra input parameters to the eval. It's just a perl
"controller" for UI separation.
/cc aszlig
On Thu, Apr 28, 2016 at 11:37 AM, wrote:
> IMO putting the logic completely into hydra
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
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, wrote:
> It can set pull request statuses (e.g. see
>
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
10 matches
Mail list logo