all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: Christopher Baines <mail@cbaines.net>
Cc: guix-devel@gnu.org
Subject: Re: Automatically building packages affected by submitted patches
Date: Mon, 04 Mar 2019 11:27:48 +0100	[thread overview]
Message-ID: <87ef7nvsrf.fsf@elephly.net> (raw)
In-Reply-To: <87tvgmfgkw.fsf@cbaines.net>

Hey Chris,

> In short, following on from some previous emails about Patchwork [1] and
> tracking and inspecting how Guix changes over time [2], I've got to the
> point where I have a very rough setup for building packages changed by
> patches sent to the guix-patches mailing list.

This is great!

> With the goal of displaying a check in Patchwork about the
> build status of the affected packages, I need to compare what's been
> build by my Cuirass instance, with what https://ci.guix.info/ has
> built. To do this, my current plan is to have the Guix Data Service
> monitor a number of Cuirass instances somehow, extract information from
> them and store it.

Would it not make sense to have the build farm perform the builds
instead of having a separate Cuirass instance?

>  - Looks at patch series in the Patchwork database that have been
>    processed through the patchwork-test-series job in Laminar.

Is the Laminar job something that could become part of Cuirass itself?

--
Ricardo

  reply	other threads:[~2019-03-04 10:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-01 21:08 Automatically building packages affected by submitted patches Christopher Baines
2019-03-04 10:27 ` Ricardo Wurmus [this message]
2019-03-04 23:12   ` Christopher Baines
2019-03-06 15:09 ` Ludovic Courtès
2019-03-06 19:39   ` Christopher Baines

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=87ef7nvsrf.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=guix-devel@gnu.org \
    --cc=mail@cbaines.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.
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.