Pushed in commit a7cf4eb6d99838606d8ecfa776f7e4920dfbb7f5 with bug fixed
and requested changes.
Thanks.
--
Mathieu Lirzin
On Wed, Oct 26, 2016 at 08:22:36PM -0400, Leo Famulari wrote:
> What does it mean for the specifications to be "re-added"? Can you
> clarify this in the docs?
I think this is a bug :-)
The specifications are stored in a database, and they may appear multiple
times, leading to duplicate evaluation
Salut !
Mathieu Lirzin skribis:
> * gnu/services/cuirass.scm: New file.
> * gnu/local.mk (GNU_SYSTEM_MODULES): Add it.
> * doc/guix.texi (Continuous integration): New node.
[...]
> +++ b/doc/guix.texi
> @@ -7687,6 +7687,7 @@ declaration.
> * Mail Services:: IMAP, POP3, SMTP, and
On Wed, Oct 26, 2016 at 03:05:58PM +0200, Mathieu Lirzin wrote:
>
> * gnu/services/cuirass.scm: New file.
> * gnu/local.mk (GNU_SYSTEM_MODULES): Add it.
> * doc/guix.texi (Continuous integration): New node.
> +In order to add build jobs you will have to set the
> +@code{specifications} field. Du
>> Is %default-cuirass-configuration needed?
>
> The benefit is a slightly more meaningful default value for #:CONFIG in
> the 'cuirass-service' procedure documentation. However I am not sure if
> that helps much. WDYT?
I don't think it's necessary. An example where it's useful is
%default-syslo
Hello David,
David Craven writes:
> Do we need to export all of these?
>
> +cuirass-configuration-cache-directory
> +cuirass-configuration-group
> +cuirass-configuration-interval
> +cuirass-configuration-database
> +cuirass-configuratio
Hi Mathieu,
Do we need to export all of these?
+cuirass-configuration-cache-directory
+cuirass-configuration-group
+cuirass-configuration-interval
+cuirass-configuration-database
+cuirass-configuration-specifications
+cuirass
* gnu/services/cuirass.scm: New file.
* gnu/local.mk (GNU_SYSTEM_MODULES): Add it.
* doc/guix.texi (Continuous integration): New node.
---
doc/guix.texi| 86 +++
gnu/local.mk | 1 +
gnu/services/cuirass.scm | 128 +
