unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Christopher Baines <mail@cbaines.net>
To: guix-devel@gnu.org
Subject: The Guix Build Coordinator in 2021
Date: Tue, 09 Feb 2021 20:30:51 +0000	[thread overview]
Message-ID: <878s7xx9tx.fsf@cbaines.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 1856 bytes --]

Hey!

Near the beginning of 2020, things changed such that I suddenly had some
time, and some of that time I spend putting idea's I'd had for a while
around building derivations, including across multiple machines, in to
practice [1].

1: https://lists.gnu.org/archive/html/guix-devel/2020-04/msg00323.html

Looking back now from 2021, I think it's been pretty successful.

In terms of building things for substitutes, the guix.cbaines.net [2]
site I setup for testing has generally had higher substitute
availability than ci.guix.gnu.org, at least for x86_64-linux, and this
is with far less compute resources.

2: http://guix.cbaines.net/

It's also allowed for massive leaps forward towards being able to
meaningfully test patches. Affected packages and system tests are now
being built, and the results of those builds are being sent to the
relevant Guix Data Service instance.

Up until recently, I've been trying to add more features. I've still got
more features in mind, but I also want to neaten up some things and pay
back some of the technical debt that's been accrued.

I've added a Roadmap section to the README file [3] if you're interested
in the specifics.

3: https://git.cbaines.net/guix/build-coordinator/about/#outline-container-orge5f01b3

Also, given that the Guix Build Coordinator is capably doing what it was
designed to do, there are problems that are now in a good position to
tackle. Things like trying to optimise substitute delivery over HTTP [4]
or otherwise, and making user interface improvements around
patchwork.cbaines.net [5] so that it's better at getting the right
information to the right people.

4: https://lists.gnu.org/archive/html/guix-devel/2021-02/msg00104.html
5: https://patchwork.cbaines.net/

If you have any comments, questions, or are interested in getting
involved, please let me know!

Thanks,

Chris

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 987 bytes --]

             reply	other threads:[~2021-02-09 20:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-09 20:30 Christopher Baines [this message]
2021-02-10 10:58 ` The Guix Build Coordinator in 2021 Mathieu Othacehe
2021-02-10 20:07   ` Christopher Baines
2021-02-10 22:29   ` 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=878s7xx9tx.fsf@cbaines.net \
    --to=mail@cbaines.net \
    --cc=guix-devel@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).