Cuirass is a continuous integration tool for Guix. It can be used both for development and for providing substitutes to others (see Substitutes).
(gnu services cuirass) module provides the following service.
The type of the Cuirass service. Its value must be a
cuirass-configuration object, as described below.
To add build jobs, you have to set the
specifications field of the
configuration. Here is an example of a service that polls the Guix repository
and builds the packages from a manifest. Some of the packages are defined in
"custom-packages" input, which is the equivalent of
(define %cuirass-specs #~(list '((#:name . "my-manifest") (#:load-path-inputs . ("guix")) (#:package-path-inputs . ("custom-packages")) (#:proc-input . "guix") (#:proc-file . "build-aux/cuirass/gnu-system.scm") (#:proc . cuirass-jobs) (#:proc-args . ((subset . "manifests") (systems . ("x86_64-linux")) (manifests . (("config" . "guix/manifest.scm"))))) (#:inputs . (((#:name . "guix") (#:url . "git://git.savannah.gnu.org/guix.git") (#:load-path . ".") (#:branch . "master") (#:no-compile? . #t)) ((#:name . "config") (#:url . "https://git.example.org/config.git") (#:load-path . ".") (#:branch . "master") (#:no-compile? . #t)) ((#:name . "custom-packages") (#:url . "https://git.example.org/custom-packages.git") (#:load-path . ".") (#:branch . "master") (#:no-compile? . #t))))))) (service cuirass-service-type (cuirass-configuration (specifications %cuirass-specs)))
While information related to build jobs is located directly in the
specifications, global settings for the
cuirass process are
accessible in other
Data type representing the configuration of Cuirass.
Location of the log file.
Location of the log file used by the web interface.
Location of the SQL queries log file. By default, SQL queries logging is disabled.
Location of the web SQL queries log file. By default, web SQL queries logging is disabled.
Location of the repository cache.
Owner of the
Owner’s group of the
Number of seconds between the poll of the repositories followed by the Cuirass jobs.
Size of the database writer queue.
Location of sqlite database which contains the build results and previously added specifications.
(* 30 24 3600))
Specifies the time-to-live (TTL) in seconds of garbage collector roots that are registered for build results. This means that build results are protected from garbage collection for at least ttl seconds.
Port number used by the HTTP server.
Listen on the network interface for host. The default is to accept connections from localhost.
A gexp (see G-Expressions) that evaluates to a list of specifications,
where a specification is an association list
(see Associations Lists in GNU Guile Reference Manual) whose
keys are keywords (
#:keyword-example) as shown in the example
This allows using substitutes to avoid building every dependencies of a job from source.
Only evaluate specifications and build derivations once.
When substituting a pre-built binary fails, fall back to building packages locally.
Extra options to pass when running the Cuirass processes.
The Cuirass package to use.
The Cuirass service configuration described above can be a little
intimidating. In particular, getting the right
can prove difficult. The
procedure offers a way to generate those
specifications and thus
setup a continuous integration server more readily.
This procedure takes a
simple-cuirass-configuration record as
argument and returns the corresponding Cuirass specifications gexp.
Data type representing the configuration of a simple Cuirass instance.
The packages to be built by Cuirass. It defaults to
means that all the discovered packages in the subsequent
field are to be selected.
It is also possible to set this field to a list of
records, so that only the packages that are part of the declared
manifests are built. This record is described below.
The name of the channel where the manifest is located.
The manifest path inside the channel.
The channels to be fetched by Cuirass (see Channels).
List the channel names that must not be searched for packages. That is often the case for the channel containing the manifest.
Build every discovered package for each system in this list. By default only the current system is selected.
Here is an example of how to setup a Cuirass instance that builds all the packages declared by Guix and a user repository. The package list is re-evaluated each time a commit is pushed in one of the declared channels.
(service cuirass-service-type (cuirass-configuration (specifications (simple-cuirass-configuration->specs (simple-cuirass-configuration (build 'all) (channels (cons (channel (name 'my-guix) (url "https://my-git-repo/guix.git")) %default-channels)))))))
In the same spirit, this builds all the packages that are part of the
my-guix channels and declared in the manifest
located in the
(service cuirass-service-type (cuirass-configuration (specifications (simple-cuirass-configuration->specs (simple-cuirass-configuration (build (list (build-manifest (channel-name 'conf) (manifest "guix/manifest.scm")))) (channels (cons* (channel (name 'my-guix) (url "https://my-git-repo/guix.git")) (channel (name 'conf) (url "https://my-git-repo/conf.git")) %default-channels)) (non-package-channels '(conf)))))))
simple-cuirass-services takes as a second optional
cuirass-configuration record. It can be used to
customize the configuration of the Cuirass instance.
(simple-cuirass-services (simple-cuirass-configuration (build 'all) (channels (cons (channel (name 'my-guix) (url "https://my-git-repo/guix.git")) %default-channels)) (non-package-channels '(conf))) (cuirass-configuration (inherit %default-cuirass-config) (host "0.0.0.0"))) ;listen on all interfaces.