Go to file
Mathieu Lirzin 7f894427b2
maint: Use absolute directory names in GUIX_PACKAGE_PATH.
This fixes "tests/hello-singleton.scm" evaluation.

* build-aux/pre-inst-env.in (GUIX_PACKAGE_PATH): Use absolute directory
names.
2016-10-23 00:11:43 +02:00
bin tests: Track Cuirass' git. 2016-09-23 16:53:07 +02:00
build-aux maint: Use absolute directory names in GUIX_PACKAGE_PATH. 2016-10-23 00:11:43 +02:00
guix tests: Track Cuirass' git. 2016-09-23 16:53:07 +02:00
src base: Handle build failure. 2016-09-23 16:53:40 +02:00
tests tests: Track Cuirass' git. 2016-09-23 16:53:07 +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: Add 'bootstrap' script. 2016-08-02 19:04:53 +02:00
README maint: Update README. 2016-08-03 02:53:13 +02:00
bootstrap build: Add 'bootstrap' script. 2016-08-02 19:04:53 +02:00
configure.ac build: Add a wrapper to 'guix environment'. 2016-08-03 02:53:12 +02:00
guix.scm tests: Track Cuirass' git. 2016-09-23 16:53:07 +02:00

README

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

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

Cuirass currently depends on the following packages:

  - GNU Guile 2.0.9 or later
  - GNU Guix (and all its development dependencies)
  - GNU Make
  - Guile-JSON
  - Guile-SQLite3
  - Git

A convenient way to install those dependencies is to install Guix and execute
the following command:

  ./build-aux/guix-env

This will build and enter an environment which provides all the necessary
dependencies.

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