mirror of https://notabug.org/mthl/cuirass.git
f65c62e53a
* guix.scm: New file; specify Guix package. * guix/ci.scm: New file; expose to Guix. * build-aux/pre-inst-env.in: Add it to GUIX_PACKAGE_PATH. * bin/evaluate.in (main): Lookup proc using name specified by #:proc. * tests/guix-track-git.scm: New file. * tests/hello-git.scm: Test it. Signed-off-by: Mathieu Lirzin <mthl@gnu.org> |
||
---|---|---|
bin | ||
build-aux | ||
guix | ||
src | ||
tests | ||
.dir-locals.el | ||
.gitignore | ||
COPYING | ||
Makefile.am | ||
README | ||
bootstrap | ||
configure.ac | ||
guix.scm |
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