Go to file
Mathieu Lirzin e58911de37
utils: Add 'alist?' procedure.
* src/cuirass/utils.scm (alist?): New procedure.
* tests/utils.scm ("alist?"): New test.
2016-07-30 23:08:39 +02:00
bin schema: Evaluations: Add 'revision' column. 2016-07-30 23:07:19 +02:00
build-aux database: Use an external SQL schema. 2016-07-25 02:12:39 +02:00
src utils: Add 'alist?' procedure. 2016-07-30 23:08:39 +02:00
tests utils: Add 'alist?' procedure. 2016-07-30 23:08:39 +02:00
.dir-locals.el evaluate: Use (cuirass ...) modules. 2016-07-25 02:37:06 +02:00
.gitignore Evaluate derivations in a separate process. 2016-07-13 14:07:24 +02:00
COPYING Initial commit. 2016-05-29 19:53:17 +02:00
Makefile.am build: Fix variable reference in comment. 2016-07-27 14:17:10 +02:00
README cuirass: Make specification argument optional. 2016-07-27 14:17:09 +02:00
configure.ac build: Check for (guix) module. 2016-07-25 13:44:25 +02:00

README

Cuirass is continuous integration system using GNU Guix.  It is
intended as replacement for Hydra.

Requirements
============

GNU Guix must be installed along with all its development dependencies
as described here:

  https://www.gnu.org/software/guix/manual/html_node/Building-from-Git.html#Building-from-Git

Its modules must be found by Guile in '%load-path'.

Example
=======

A quick way to manually test Cuirass is to execute:

  ./pre-inst-env cuirass --specifications=tests/hello-singleton.scm --database=test.db

This will read the file "tests/hello-singleton.scm" which contains a list of
specifications and add them to the database "test.db" which is created if it
doesn't already exist.

cuirass then loops evaluating/building the specs.  The database keeps track of
the specifications in order to allow users to accumulate specifications.  To
resume the evaluation/build process you can execute the same command without
the specifications option:

  ./pre-inst-env cuirass --database=test.db