guix-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Advice about GuixSD on Serveraptor?


From: Ludovic Courtès
Subject: Re: Advice about GuixSD on Serveraptor?
Date: Sun, 26 Mar 2017 12:20:04 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1 (gnu/linux)

Leo Famulari <address@hidden> skribis:

> On Fri, Mar 24, 2017 at 10:36:08AM +0100, Ludovic Courtès wrote:
>> Hi!
>> 
>> Leo Famulari <address@hidden> skribis:
>> 
>> > On Wed, Mar 22, 2017 at 01:20:53PM -0400, Leo Famulari wrote:
>> >> It's not a bad idea to build it on Hydra. Hydra already builds a
>> >> usb-image / disk-image job [0], so we could add a qemu-image job, too.
>> >
>> > Actually, we used to build a qemu-image on Hydra, but we removed because
>> > it was troublesome and unused.
>> >
>> > https://git.savannah.gnu.org/cgit/guix.git/commit/?id=a3a27745013f3e5a287de3bf0187b2f72beb6965
>> >
>> > Maybe we should try again :)
>> 
>> Yup, we could reinstate it if needed.  That said, we wouldn’t too many
>> downloads from hydra.gnu.org…
>
> If we took that route, I'd point the Serveraptor admin to the Hydra link
> and ask them to download it once themselves, rather than having each
> client download it.
>
> But, making a qemu-image at each evaluation is not so good for
> general distribution, because we won't have tested it as thoroughly as
> the release image. We'd want the qemu-image to build only if all the
> system tests passed.

Yeah I think recent Hydra can present a release page if and only if some
other derivations also succeeded with the same commit.

Anyway, let us know what you think is the right approach for now!

Thanks,
Ludo’.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]