[Nix-dev] github triggered builds

[Domen Kožar]

There is also https://github.com/mayflower/nixbot

On Wed, May 10, 2017 at 11:27 AM, Maarten Hoogendoorn <maarten at moretea.nl>
wrote:

> I'm interested in this area as well.
>
> Graham wrote some tooling to enable hydra to build PR's (
> https://github.com/grahamc/hydra-prs/). Combined with a github bot this
> is getting close to what you're aiming for. (The bot is necessary given
> that we don't want to run any PR without a manual code review on this
> public project).
>
>
> 2017-05-09 22:44 GMT+02:00 Harmen <harmen at lijzij.de>:
>
>> On Tue, May 09, 2017 at 01:08:08PM +0200, Maarten Hoogendoorn wrote:
>> > Unfortunately this does not really help with sharing derivations that
>> have
>> > been built before.
>>
>> Thanks for all the replies. Seems like I didn't miss anything obvious.
>>
>> My current plan is to try gitlab with my own runner, which has a 'shell
>> executor' option.
>> https://docs.gitlab.com/runner/executors/shell.html
>> That looks like to be exactly what I need for nix based builds.
>>
>>
>> Is this use-case of nix so uncommon (push-triggered builds)? Do most
>> people go for Hydra?
>>
>> Thanks!
>> Harmen
>>
>> >
>> > 2017-05-09 10:02 GMT+02:00 zimbatm <zimbatm at zimbatm.com>:
>> >
>> > > Travis CI also has support for nix builds and might be easier to
>> setup.
>> > >
>> > > On Mon, 8 May 2017, 18:17 Tomasz Czyż, <tomasz.czyz at gmail.com> wrote:
>> > >
>> > >> https://nixos.org/hydra/
>> > >>
>> > >> and
>> > >>
>> > >> https://github.com/hercules-ci/hercules ( looks like still in heavy
>> > >> development but maybe usable :))
>> > >>
>> > >> 2017-05-08 18:14 GMT+01:00 Harmen <harmen at lijzij.de>:
>> > >>
>> > >>> Hi,
>> > >>>
>> > >>> I'm trying to see how I can make my build processes easier with
>> nix. So
>> > >>> far
>> > >>> it's going pretty good and it's fun, although there was a lot of
>> > >>> searching
>> > >>> online for scattered documents.
>> > >>>
>> > >>> Want I want to do (as the first thing to change to nix in
>> production) is
>> > >>> to
>> > >>> port the building of some docker images I use for testing. The idea
>> is to
>> > >>> have docker images build, tagged with their branch they come from,
>> when
>> > >>> someone
>> > >>> pushes something. The building and pushing an sich work. The .nix
>> files
>> > >>> live in
>> > >>> the repo, and with a `make docker` the image is build and uploaded.
>> I'm
>> > >>> very
>> > >>> happy to be able to build docker images without actually having to
>> use
>> > >>> docker
>> > >>> ;)
>> > >>>
>> > >>> So, what would be the recommended way to trigger the building
>> process?
>> > >>> I'm
>> > >>> currently using drone.io, but that works with containers. It works
>> with
>> > >>> nix,
>> > >>> when I give it the nixos/nix docker image, but building a node
>> project
>> > >>> takes
>> > >>> about 5 minutes, and drags in way too much from cache.nixos.org. I
>> > >>> tried to
>> > >>> have it make a local nix binary-cache, but there are some problems
>> > >>> there, but
>> > >>> drone also just doesn't fit the problem nicely.  Nix solves the
>> problem
>> > >>> of
>> > >>> versioning so much nicer than containers that I would prefer to use
>> > >>> something
>> > >>> simpler. Hydra could work, but I'm a bit intimidated by that, and
>> would
>> > >>> like to
>> > >>> have something simpler for now.
>> > >>>
>> > >>> The LT;DR: question: is there a simple nix based build system which
>> can
>> > >>> be
>> > >>> triggered via git{hub,lab} hooks?
>> > >>>
>> > >>>
>> > >>> Thanks!
>> > >>> Harmen
>> > >>> (If there is a better place to ask this, let me know)
>> > >>> _______________________________________________
>> > >>> nix-dev mailing list
>> > >>> nix-dev at lists.science.uu.nl
>> > >>> https://mailman.science.uu.nl/mailman/listinfo/nix-dev
>> > >>>
>> > >>
>> > >>
>> > >>
>> > >> --
>> > >> Tomasz Czyż
>> > >> _______________________________________________
>> > >> nix-dev mailing list
>> > >> nix-dev at lists.science.uu.nl
>> > >> https://mailman.science.uu.nl/mailman/listinfo/nix-dev
>> > >>
>> > >
>> > > _______________________________________________
>> > > nix-dev mailing list
>> > > nix-dev at lists.science.uu.nl
>> > > https://mailman.science.uu.nl/mailman/listinfo/nix-dev
>> > >
>> > >
>>
>
>
> _______________________________________________
> nix-dev mailing list
> nix-dev at lists.science.uu.nl
> https://mailman.science.uu.nl/mailman/listinfo/nix-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.science.uu.nl/pipermail/nix-dev/attachments/20170510/758adc16/attachment-0001.html>