Go to file
Mathieu Lirzin cbdb59af8e
doc: Add Cuirass manual.
* doc/cuirass.texi: New file.
* doc/fdl-1.3.texi: Likewise.
* Makefile.am (info_TEXINFOS, doc_cuirass_TEXINFOS): New variables.
* dir-locals.el: Use the American dictionary for Texinfo mode.
* .gitignore: Update.
2016-12-04 22:31:03 +01:00
bin cuirass: Hard code Guile load paths. 2016-11-12 17:49:20 +01:00
build-aux cuirass: Hard code Guile load paths. 2016-11-12 17:49:20 +01:00
doc doc: Add Cuirass manual. 2016-12-04 22:31:03 +01:00
guix tests: Track Cuirass' git. 2016-09-23 16:53:07 +02:00
src base: Create the parent directories of '%package-cachedir'. 2016-12-01 20:59:43 +01:00
tests db: Forbid inserting the same specification twice. 2016-11-17 01:19:05 +01:00
.dir-locals.el doc: Add Cuirass manual. 2016-12-04 22:31:03 +01:00
.gitignore doc: Add Cuirass manual. 2016-12-04 22:31:03 +01:00
COPYING Initial commit. 2016-05-29 19:53:17 +02:00
Makefile.am doc: Add Cuirass manual. 2016-12-04 22:31:03 +01:00
README maint: Update README. 2016-10-26 14:16:36 +02:00
bootstrap build: Add 'bootstrap' script. 2016-08-02 19:04:53 +02:00
configure.ac maint: Add copyright notices for the build system. 2016-11-12 17:58:17 +01:00
guix.scm tests: Track Cuirass' git. 2016-09-23 16:53:07 +02:00

README

Cuirass is a continuous integration tool using GNU Guix.  It is intended as a
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