all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: David Craven <david@craven.ch>
To: Mark H Weaver <mhw@netris.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: [GSoC] Continuous integration tool à la Hydra.
Date: Sat, 6 Aug 2016 18:58:27 +0200	[thread overview]
Message-ID: <CAL1_im=xg0dbd3oz2a0Un+Ma43m7aX+7Wic19mi2S-CZ1pE=Lw@mail.gmail.com> (raw)
In-Reply-To: <CAL1_immomHk6Dz+7JD63HFvsF+a38w+6iRBvbDT6hy6zqZ_KVQ@mail.gmail.com>

> I understand that, but developers should have a simple way to check
> their own work. Hopefully commits made to master are good commits
> and hydra only has to rebuild from HEAD.

It would also be nice if developers could easily hook up their servers to
the guix build farm, if I do run my own continuous integration system,
my server would be idling most of the time anyway, so it would be
nice to use that time.

  reply	other threads:[~2016-08-06 16:58 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-06 11:05 [GSoC] Continuous integration tool à la Hydra David Craven
2016-08-06 16:19 ` Mark H Weaver
2016-08-06 16:23   ` David Craven
2016-08-06 16:58     ` David Craven [this message]
2016-08-06 23:45 ` Mathieu Lirzin
  -- strict thread matches above, loose matches on Subject: below --
2016-05-29 20:10 Mathieu Lirzin
2016-05-30 21:34 ` Ludovic Courtès
2016-05-30 21:54 ` Ludovic Courtès
2016-06-20 22:44 ` Mathieu Lirzin
2016-06-24 12:42   ` Ludovic Courtès
2016-07-25  0:30 ` Mathieu Lirzin
2016-07-25 21:36   ` Ludovic Courtès
2016-07-27 14:28     ` Mathieu Lirzin
2016-07-28 12:38       ` Ludovic Courtès
2016-07-29 11:20     ` Florian Paul Schmidt
2016-07-29 19:26       ` Mathieu Lirzin
2016-07-30 22:49         ` Ludovic Courtès
2016-07-31  7:09         ` Florian Paul Schmidt
2016-07-31 12:03           ` Mathieu Lirzin
2016-08-01 18:55             ` Florian Paul Schmidt

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='CAL1_im=xg0dbd3oz2a0Un+Ma43m7aX+7Wic19mi2S-CZ1pE=Lw@mail.gmail.com' \
    --to=david@craven.ch \
    --cc=guix-devel@gnu.org \
    --cc=mhw@netris.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.