From: zimoun <zimon.toutoune@gmail.com>
To: Kyle Andrews <kyle@posteo.net>, help-guix@gnu.org
Subject: Re: How to offload builds only when some of the offload build servers are available
Date: Mon, 02 May 2022 10:37:12 +0200 [thread overview]
Message-ID: <874k28ba9z.fsf@gmail.com> (raw)
In-Reply-To: <875ympmdqw.fsf@posteo.net>
Hi,
On Sun, 01 May 2022 at 16:01, Kyle Andrews <kyle@posteo.net> wrote:
> How can I configure the offload functionality to check whether the build
> machines specifiec in ~/etc/guix/machines.scm~ are available first; and
> if they are not (e.g. because I am roaming outside my local network)
> just proceed with builds locally so that I don't have to remember to
> pass --no-offload?
As discussed in this old and still open bug#24496 [1], you could do
something like that for ’/etc/guix/machines.scm’:
--8<---------------cut here---------------start------------->8---
(define the-machine (build-machine …))
(if (managed-to-connect-timely the-machine)
(list the-machine)
'())
--8<---------------cut here---------------end--------------->8---
where ’managed-to-connect-timely’ could be a plain ’system*’ call via
’ping’ to the target offload machine. Guile probably provides a better
interface for network check. :-)
However, note that it could be nice to have something dynamically
handled [2] by the daemon. Feature missing…
1: <https://issues.guix.gnu.org/issue/24496#3>
2: <https://yhetil.org/guix/86zgp0hec6.fsf@gmail.com>
Cheers,
simon
prev parent reply other threads:[~2022-05-02 9:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-01 16:01 How to offload builds only when some of the offload build servers are available Kyle Andrews
2022-05-01 17:24 ` raingloom
2022-05-02 8:37 ` zimoun [this message]
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=874k28ba9z.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=help-guix@gnu.org \
--cc=kyle@posteo.net \
/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.
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).