all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Christopher Baines <mail@cbaines.net>
To: guix-devel@gnu.org
Subject: Moving forward with testing patches and branches
Date: Fri, 11 Feb 2022 10:46:35 +0000	[thread overview]
Message-ID: <87zgmxd4aq.fsf@cbaines.net> (raw)

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

Hey!

I think the last thread I started on this topic was all the way back in
August [1].

1: https://lists.gnu.org/archive/html/guix-devel/2021-08/msg00001.html

Building on the feedback there, I've got two threads of work in mind for
the start of this year.

Firstly, work on getting data from the data service about patch series
and branches out to places where it's useful. Several ideas came up in
[1], I think all of them need doing/trying.

The patch testing setup centred around [2] is operating again, and at
least producing information on lint warnings and affected packages, so
work can proceed on trying to make use of that information.

2: https://patches.guix-patches.cbaines.net/project/guix-patches/list/

The second thread of work is to get builds happening again and
populating the data service with information. While there's the option
to setup a separate build coordinator instance as before, I first want
to get the bordeaux.guix.gnu.org build farm building things from patches
and non-master branches.

I think the main prerequisite for this changing the
data.guix-patches.cbaines.net to data.qa.guix.gnu.org (or something
similar, just so it's a stable URL). Once that has happened, the agents
can be configured to support fetching derivations from
data.qa.guix.gnu.org as well as data.guix.gnu.org. I'm hoping to start
working on this within the next week or two.

Let me know if you have any thoughts or questions!

Thanks,

Chris

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

                 reply	other threads:[~2022-02-11 11:41 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=87zgmxd4aq.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 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.