From: ludo@gnu.org (Ludovic Courtès)
To: "Clément Lassieur" <clement@lassieur.org>
Cc: guix-devel@gnu.org, guix-sysadmin@gnu.org
Subject: Re: 01/01: hydra: services: Fix Cuirass configuration.
Date: Fri, 20 Jul 2018 23:22:02 +0200 [thread overview]
Message-ID: <87muulob5x.fsf@gnu.org> (raw)
In-Reply-To: <20180720182935.45B8E204A2@vcs0.savannah.gnu.org> (ClXment Lassieur's message of "Fri, 20 Jul 2018 14:29:35 -0400 (EDT)")
Howdy Clément,
clement@lassieur.org (ClXment Lassieur) skribis:
> commit 641b9750c30cd8275765aaa6457aea961224f928
> Author: Clément Lassieur <clement@lassieur.org>
> Date: Fri Jul 20 20:10:28 2018 +0200
>
> hydra: services: Fix Cuirass configuration.
>
> * hydra/modules/sysadmin/services.scm (guix-input): Take a NAME argument.
> (cuirass-specs): Use the correct input names. Rename '#:proc-arguments' to
> '#:proc-args'. Add specifications for the "staging" and "core-updates"
> branches. Add missing '#:load-path-inputs' and '#:package-path-inputs'
> fields.
> ---
> hydra/modules/sysadmin/services.scm | 35 ++++++++++++++++++++++++++---------
Thanks a lot for fixing it! Cuirass is back up and running now on
berlin.
One question: could we have a single “guix” input corresponding to
https://git…/guix.git for the master branch? I suppose that should work
in theory?
Anyway the database migration went smoothly and the new schema looks
much better. Thank you!
Ludo’.
next parent reply other threads:[~2018-07-20 21:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180720182934.2138.94704@vcs0.savannah.gnu.org>
[not found] ` <20180720182935.45B8E204A2@vcs0.savannah.gnu.org>
2018-07-20 21:22 ` Ludovic Courtès [this message]
2018-07-20 23:07 ` 01/01: hydra: services: Fix Cuirass configuration Clément Lassieur
2018-07-23 12:58 ` Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87muulob5x.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=clement@lassieur.org \
--cc=guix-devel@gnu.org \
--cc=guix-sysadmin@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).