configure

Queued Started Finished

Reproduce this run
Timing
  1. 0.00 s $ /nix/store/kwc34h21my8mf7xbqm9gxs1xfx07xb4i-coreutils-9.11/bin/timeout --kill-after=15s 7200s /nix/store/ckxcj4hnq3qf76prhlld3hbl3z2wb84i-nix-ci-config-0.0.0/bin/nix-ci-config --flake git+https://github.com/mtlynch/picoshare?ref=refs%2Fpull%2F842%2Fhead&rev=43b875ecf2a73e6e51bc96449bf5040b452be334 --forge-type github
  2. 0.20 s Read flake.nix over the forge file API in 2 request(s), then fetched the flake in full to evaluate its nix-ci output.
  3. 0.21 s No nix-ci configuration found, continuing with default configuration.
  4. 0.21 s
  5. 0.21 s WARNING: If you are seeing a 'Cannot find Git revision' failure in a show job, be sure to configure git-ssh-key in your nix-ci configuration file.
  6. 0.21 s Configuration accepted.

Effective configuration

What this suite's inherited settings came to, and what decided each of them.

How a setting is inherited

What to build

Build whichever system s the relevant workers are configured to build.

Only build: Everything

But exclude: Nothing

How to build

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.

Also set false for an in-repo test or deploy job that reads the history of its checkout.

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