From: Jan Nieuwenhuizen <janneke@gnu.org>
To: "Thompson\, David" <dthompson2@worcester.edu>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: Setting up CI for Guile
Date: Thu, 06 Oct 2016 17:16:11 +0200 [thread overview]
Message-ID: <87lgy1v77o.fsf@gnu.org> (raw)
In-Reply-To: <CAJ=RwfZQ+8FGB+NHJstPRjkQd=ZAwy+ekm-_Wrv-B2FSJrfomQ@mail.gmail.com> (David Thompson's message of "Thu, 6 Oct 2016 10:34:39 -0400")
Thompson, David writes:
>> I'm a big fan of CI (automated testing), and maybe you are too. I'd
>> love to have CI for reviewing patches of Guile.
>
> This is a good idea.
+1
> That's unfortunate. It's important to build from scratch, which means
> bootstrapping the compiler, which indeed takes awhile, but patches
> generally take days or longer to be reviewed and merged so a few hours
> is no big deal, IMO. The GNU Guix project is working on a replacement
> for its current CI system at hydra.gnu.org that runs Hydra from the
> Nix project, named Cuirass, so I think we should try to use that
> instead of GitLab.
I so much like this idea, that I contributed some patches to Cuirass to
do exactly this. Next to being a CI dedicated for GuixSD to track any
package's git. Here's the discussion
https://lists.gnu.org/archive/html/guix-devel/2016-09/threads.html#01338
patches are in Cuirass now and anyone is much encouraged to play.
> I think this is a wonderful idea that could use a new implementation.
> Thanks for getting the ball rolling with the proof-of-concept!
Yes!
Greetings,
Jan
--
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.nl
next prev parent reply other threads:[~2016-10-06 15:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-06 4:26 Setting up CI for Guile Wilfred Hughes
2016-10-06 9:43 ` Taylan Ulrich Bayırlı/Kammer
2016-10-06 14:34 ` Thompson, David
2016-10-06 15:16 ` Jan Nieuwenhuizen [this message]
2016-10-11 19:56 ` Ludovic Courtès
2016-10-18 1:39 ` Mike Gerwitz
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://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lgy1v77o.fsf@gnu.org \
--to=janneke@gnu.org \
--cc=dthompson2@worcester.edu \
--cc=guile-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.
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).