Wasn't the plan to upload the binaries automatically to resolve the disk
space issue on the workers ?
Or is this another cache.
On Wed, 25 Nov 2015 at 09:24 Vladimír Čunát wrote:
> On 11/24/2015 10:48 PM, zimbatm wrote:
> > Master would already have binary caches from the
On 11/25/2015 06:45 PM, zimbatm wrote:
> Wasn't the plan to upload the binaries automatically to resolve the disk
> space issue on the workers ?
Yes, that's what Eelco said IIRC, and it would be a great improvement, I
believe, but so far it's only a plan AFAIK.
Vladimir
smime.p7s
this will happen in very short future via pull requests being built by hydra
instead of travis. then we would not have to worry about binary cache anyway.
eelco was working on this at the sprint after nixcon and i guess once he
polishes he'll make the announcement and release it.
Quoting
On 11/24/2015 10:48 PM, zimbatm wrote:
> Master would already have binary caches from the builds so we could use
> it as the unstable channel.
The main problem here is that binaries only get to the binary cache when
the channel updates, which means the tests have to succeed, etc.
Vladimir
The Homu model looks quite interesting. If homu would trigger a hydra build
and only push to master after the build succeeds, I believe that it would
simplify a lot of things nicely.
Master would already have binary caches from the builds so we could use it
as the unstable channel. This is quite
It seems someone added this to the nixpkgs! Awesome!
On 22-11-2015 17:09:43, Matthias Beyer wrote:
> Hi,
>
> I wanted to ask whether it would be a good idea to use montion-bot[0] for our
> nixpkgs repository?
>
> Another idea would be to use homu[1]. Please argue.
>
> [0]:
Hi,
I wanted to ask whether it would be a good idea to use montion-bot[0] for our
nixpkgs repository?
Another idea would be to use homu[1]. Please argue.
[0]: https://github.com/facebook/mention-bot
[1]: homu.io
--
Mit freundlichen Grüßen,
Kind regards,
Matthias Beyer
Proudly sent with mutt.