CI and devshell comments say what the config does: jobTimeout bounds jobs, coverage runs nightly, dead timeout keys removed
Job-level timeout-minutes is parsed but not enforced by this runner; only the runner's jobTimeout bounds a job. Also fixes the devshell coverage comment, the shellcheck job comment, an option description citing a script that is not in the repo, and comment file pointers that resolve to nothing.
This commit is contained in:
parent
fefc565794
commit
2644c0d5f9
7 changed files with 20 additions and 27 deletions
|
|
@ -40,7 +40,7 @@ let
|
|||
# reach the store, and waiting on a login to that store would take that
|
||||
# path down whenever it is sealed. There the gateway starts on the hive
|
||||
# leaf, or on a host without a hive on a throwaway self-signed pair
|
||||
# (../hive-gateway/default.nix), and the issuing script re-imports the
|
||||
# (./hive-gateway/default.nix), and the issuing script re-imports the
|
||||
# services leaf into the running nginx once it lands.
|
||||
#
|
||||
# Nor on a host fronting no swarm name: it asks the store for the root
|
||||
|
|
@ -51,7 +51,7 @@ let
|
|||
|
||||
# The hive leaf, `hive-tls-resign` and the hive identity it needs exist only
|
||||
# where a hive runs. A gateway host without one serves the swarm-services
|
||||
# leaf in their place (../hive-gateway/default.nix).
|
||||
# leaf in their place (./hive-gateway/default.nix).
|
||||
runsHive = hyperhiveCfg.deploy.hive-controller.enable;
|
||||
|
||||
# The gateway's own leaf is only issued when the gateway actually serves a
|
||||
|
|
|
|||
Loading…
Reference in a new issue