Queued Started Finished
What this suite's inherited settings came to, and what decided each of them.
Build whichever
system
s
the relevant workers are configured to build.
Only build: Everything
But exclude: Nothing
enable
:
true
Whether to run CI.
timeout
:
null
Maximum timeout, in seconds.
Note that the actual timeout may depend on the workers' configuration.
Set to null for a suite that runs without a timeout of its own.
allow-import-from-derivation
:
true
Allow import-from-derivation during evaluation.
shallow-clone
:
true
Fetch only the commit being built, not its whole history.
Set false for a flake that reads self.revCount, which has nothing to count without the history.
In-repo test and deploy jobs ignore this and fetch the whole history.
impure
:
false
Build with --impure
build-logs
:
true
Build with --print-build-logs
fail-fast
:
true
Cancel the rest of a suite once one job fails
auto-retry
:
true
Automatically retry every individual failed run in a suite once
fail-on-dangling-dependencies
:
false
Fail the build when a configured build dependency references a job that does not exist.
When false, such a dangling dependency is reported as a warning and ignored instead.
dependency-discovery
:
true
Dependency discovery configuration
release-to-hackage
Deployment is enabled
Package:
packages.x86_64-linux.release-to-hackage
System: guessed based on the package:
x86_64-linux
Deployment is allowed from:
master
In repo:disabled
(default)
Shallow clone: True
These secrets are required for to the deployment:
HACKAGE_API_KEY
These ssh keys are required for the deployment: