configure

Reproduce this run
  1. 0.73 s $ /nix/store/9ypz3flqsrl5xl495mm8h645gadjsxi1-coreutils-9.11/bin/timeout --kill-after=15s 7200s /nix/store/p6gjvnswdnw7sngaza9rhmfc1whaxhij-nix-ci-config-0.0.0/bin/nix-ci-config --flake git+https://codeberg.org/mtlynch/go-app-starter?ref=master&rev=7fb4ca2d138d0a53dd4470fb1e89d04a8f03a8e7 --forge-type forgejo
  2. 0.75 s Read the configuration over the forge file API in 2 request(s).
  3. 0.75 s
  4. 0.75 s Configured jobs with configuration:
  5. 0.75 s {
  6. 0.75 s "deploy": {
  7. 0.75 s "fly": {
  8. 0.75 s "in-repo": true,
  9. 0.75 s "package": "packages.x86_64-linux.deploy-to-fly",
  10. 0.75 s "secrets": [
  11. 0.75 s "FLY_API_TOKEN"
  12. 0.75 s ],
  13. 0.75 s "system": "x86_64-linux"
  14. 0.75 s }
  15. 0.75 s }
  16. 0.75 s }
  17. 0.75 s
  18. 0.85 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.

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

Deploy Configurations

Deploy fly

Deployment is enabled

Package: packages.x86_64-linux.deploy-to-fly

System: x86_64-linux

Deployment is allowed from: :default

In repo:enabled

Shallow clone: False

These secrets are required for to the deployment:

These ssh keys are required for the deployment: