| Age | Commit message (Collapse) | Author |
|---|
|
The forge-laminar service should require the laminar service, and
transparently set it up even if the user has not explicitly specified
it.
* forge/laminar.scm: Import (gnu services ci).
(forge-laminar-service-type): Extend laminar-service-type with a
dummy value, thus requiring it.
|
|
These fields need to be thunked to allow the user access to
this-record accessors when describing jobs.
* forge/forge.scm (<forge-project-configuration>)[ci-jobs]: Thunk
field.
* forge/laminar.scm (<forge-laminar-job>)[run]: Thunk field.
|
|
Predicates are also a part of the public interface of a record type
and are sometimes required.
* forge/forge.scm: Export predicates forge-configuration?,
forge-project-configuration? and forge-derivation-job?.
* forge/laminar.scm: Export predicate forge-laminar-configuration?.
|
|
These this-record accessors will be required in thunked fields.
* forge/forge.scm (<forge-project-configuration>): Add
this-forge-project-configuration accessor and export it. Use it
instead of this-record in the default value of the ci-jobs-trigger
field.
* forge/laminar.scm (<forge-laminar-job>): Add this-forge-laminar-job
accessor and export it.
|
|
* forge/laminar.scm (forge-laminar-activation): Create laminar
configuration directory if it does not exist.
|
|
* forge/laminar.scm: Rename all guix-laminar-* names to
forge-laminar-*.
* forge/forge.scm (forge-activation, forge-service-type): Replace
guix-laminar-job-name with forge-laminar-job-name.
(forge-service-type): Replace guix-laminar-service-type with
forge-laminar-service-type and guix-laminar-group with
forge-laminar-group.
|
|
|
