all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Sree Harsha Totakura <sreeharsha@totakura.in>
Cc: Guix Development <Guix-devel@gnu.org>
Subject: Re: New Hydra build slaves
Date: Tue, 04 Mar 2014 17:47:55 +0100	[thread overview]
Message-ID: <874n3duczo.fsf@gnu.org> (raw)
In-Reply-To: <5315C1B7.20803@totakura.in> (Sree Harsha Totakura's message of "Tue, 04 Mar 2014 13:06:15 +0100")

Sree Harsha Totakura <sreeharsha@totakura.in> skribis:

> On 03/04/2014 12:12 PM, Ludovic Courtès wrote:

[...]

>> I was actually thinking of general Hydra administration.
>> Occasionally machines may have troubles, like transient errors
>> (networking, disk space, random build issues, etc.) requiring manual
>> intervention, or occasional Hydra upgrades.
>
> OK, I can do these.

Excellent!  We can discuss the details off-line, possibly with Andreas
and Nikita, who have already suffe^W had the opportunity to help.  :-)

>> There’s also the problem that our current setup is fairly hackish. 
>> Having scripts to automate some of the tasks would be an
>> improvement.
> We can try setting up some kinda monitoring on the buildslaves which can
> then send emails when problems arise.  WDYT?

Yes, that would be great.

Also, I hope these can be the first machines to run the full GNU.  For
that, we’ll need service definitions for a few more things, notably
Hydra, for the front-end.

Thanks,
Ludo’.

  reply	other threads:[~2014-03-04 16:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-03 22:31 New Hydra build slaves Ludovic Courtès
2014-03-04  9:32 ` Sree Harsha Totakura
2014-03-04 11:12   ` Ludovic Courtès
2014-03-04 12:06     ` Sree Harsha Totakura
2014-03-04 16:47       ` Ludovic Courtès [this message]
2014-03-04 12:11     ` Alex Sassmannshausen
2014-03-04 16:50       ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=874n3duczo.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=Guix-devel@gnu.org \
    --cc=sreeharsha@totakura.in \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.