unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Mathieu Othacehe <othacehe@gnu.org>
To: Christopher Baines <mail@cbaines.net>
Cc: guix-devel@gnu.org, guix-maintainers@gnu.org
Subject: Re: Project direction with testing changes (branches and patches)
Date: Tue, 10 Aug 2021 08:04:18 +0200	[thread overview]
Message-ID: <87im0d96ot.fsf@gnu.org> (raw)
In-Reply-To: <87r1f2i82z.fsf@cbaines.net> (Christopher Baines's message of "Mon, 09 Aug 2021 23:09:24 +0100")


Hello Chris,

> I think trying to change up how branches (staging/core-updates) are
> tested is a good place to start. The concrete change I'm proposing is to
> use an instance of the Guix Data Service plus an instance of the Guix
> Build Coordinator to do the testing and builds, rather than Cuirass on
> ci.guix.gnu.org which is the current approach.
>
> The main advantages of that would be the comparison support from the
> Guix Data Service, and the build performance and reliability that the
> Guix Build Coordinator brings. The main disadvantage is probably the
> lack of an admin like interface similar to that of Cuirass (I think this
> can be remedied in the medium term though).

We indeed desperately need some more automation. For each new patch
series, it would be great to have the following information:

* Status of the linter.
* Status of the depending derivations.
* Status of the unit tests (in the tests/ directory).
* Status of the system tests (in the gnu/tests/ directory).

I would like to stay focused on the existing, well adopted solutions and
build upon them.  With Cuirass we already have most of the machinery to
provide those information.

In addition, we have dashboards, RSS and email notification support
which could allow us to extend Cuirass functionalities to provide the
expected CI features.

We could imagine a new API such as /api/changeset/new that would create
temporary Cuirass specifications. The output result could be consulted
using a new /api/changeset/status API or directly through the Cuirass
web interface. Cuirass could also send email and RSS notifications on
that changeset.

Those APIs could be used by Mumi to trigger the /api/changeset/new API
notification on one hand and to display some status using the
/api/changeset/status API on the other hand.

I think that this whole infrastructure is just a few Guile modules away
and if we could involve more fellow hackers in the process, it would be
just great.

Thanks,

Mathieu


  reply	other threads:[~2021-08-10  6:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-01 11:50 Project direction with testing changes (branches and patches) Christopher Baines
2021-08-04 21:15 ` Ludovic Courtès
2021-08-09 22:09   ` Christopher Baines
2021-08-10  6:04     ` Mathieu Othacehe [this message]
2021-08-10 19:26       ` Christopher Baines
2021-08-11 10:37         ` Ludovic Courtès
2021-08-11 22:27           ` Christopher Baines
2021-08-10  7:05     ` Ricardo Wurmus
2021-08-12  8:04 ` Lars-Dominik Braun

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=87im0d96ot.fsf@gnu.org \
    --to=othacehe@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=guix-maintainers@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 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).