unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Mathieu Othacehe <othacehe@gnu.org>
To: zimoun <zimon.toutoune@gmail.com>
Cc: 45006@debbugs.gnu.org
Subject: [bug#45006] cuirass: Add remote build support.
Date: Mon, 21 Dec 2020 14:40:36 +0100	[thread overview]
Message-ID: <87wnxb2s6j.fsf@gnu.org> (raw)
In-Reply-To: <86pn3s1mbu.fsf@gmail.com> (zimoun's message of "Wed, 02 Dec 2020 12:25:41 +0100")


Hello,

There's a new variant of this patch on the wip-offload branch of
Cuirass. Quite a few things have changed since the first version:

* The "remote-server" no longer communicates directly with Cuirass, all
  the exchanges are done through the database.

* The "remote-worker" now honors "timeout" and "max-silent-time" package
  parameters.

* I have added build priorities support. The build priority is computed
  this way:

build_priority = specification_priority * 10 + package_priority

* There's a new "worker" table that stores what workers are currently
  building, and an associated "/workers" page.

* The "remote-worker" can connect to a "remote-server" specified on the
  command line.

* The substitutes are downloaded and stored in the publish cache directory.

I have deployed another Cuirass instance on berlin using this mechanism
and workers on all build machines. It's been building
master/core-updated/staging/modular specifications since a few days for
x86_64-linux and i686-linux architectures.

The results are really better than using the current implementation and
it should be possible to transition to this new architecture soon.

Thanks,

Mathieu




  reply	other threads:[~2020-12-21 13:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-02 11:04 [bug#45006] cuirass: Add remote build support Mathieu Othacehe
2020-12-02 11:25 ` zimoun
2020-12-21 13:40   ` Mathieu Othacehe [this message]
2020-12-21 14:13     ` zimoun
2020-12-21 15:08       ` Mathieu Othacehe
2020-12-21 16:41         ` zimoun

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=87wnxb2s6j.fsf@gnu.org \
    --to=othacehe@gnu.org \
    --cc=45006@debbugs.gnu.org \
    --cc=zimon.toutoune@gmail.com \
    /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).