From: Danny Milosavljevic <dannym@scratchpost.org>
To: <guix-devel@gnu.org>
Subject: Continuous integration - automatic EMAIL
Date: Wed, 7 Oct 2020 17:39:35 +0200 [thread overview]
Message-ID: <20201007173935.3f5ee457@scratchpost.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1088 bytes --]
Hi,
please, let's improve building and testing processes.
Please, can we have the build servers send build failures to guix-devel
instead of hoping that people check manually? I have other things to do
in my life than to poll random servers every few hours.
If you don't want to send e-mail on all failures (probably an overwhelming
flood at first--that's how bad the current state is!), then I suggest to:
Daily do, on each supported architecture (and I mean those packages
specifically--it's not an example stand-in):
guix pull
guix build glibc || mail guix-devel@gnu.org -s "glibc failed"
guix build gtk+ || mail guix-devel@gnu.org -s "gtk+ failed"
guix build gnome-desktop || mail guix-devel@gnu.org -s "gnome-desktop failed"
and I mean automatically--not triggered manually by a person.
Maybe I'm missing something--but the amount of manual fiddling I have to do
which a computer could automate perfectly well is REALLY inefficient.
There's nothing fundamental missing--why can't the last obvious step be
added so it is actually automatic?
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2020-10-07 15:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-07 15:39 Danny Milosavljevic [this message]
2020-10-07 15:52 ` Continuous integration - automatic EMAIL Mathieu Othacehe
2020-10-12 12:06 ` Ludovic Courtès
2020-10-12 19:12 ` zimoun
2020-10-13 13:59 ` Ludovic Courtès
2020-10-07 22:20 ` raingloom
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=20201007173935.3f5ee457@scratchpost.org \
--to=dannym@scratchpost.org \
--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).