ci: internal jobs skip on the public forge instead of waiting for a hive-ci runner
Some checks were skipped
public bin cache / build + push to preem:grid (push) Has been skipped
Some checks were skipped
public bin cache / build + push to preem:grid (push) Has been skipped
A job-level if: is evaluated by whichever runner picks the job up. The public forge's copy has only a nixos runner, so a job guarded by if: vars.PUBLIC_FORGE != 'true' and pinned to runs-on: [hive-ci] never gets picked up there to evaluate the guard at all - it just sits queued. runs-on now carries the same PUBLIC_FORGE variable: hive-ci internally, nixos on the public copy. There the nixos runner picks the job up, evaluates the existing if:, and skips it immediately. Internally PUBLIC_FORGE is unset, so runs-on still resolves to hive-ci and nothing changes.
This commit is contained in:
parent
e94406cdb9
commit
a86379eac5
3 changed files with 11 additions and 11 deletions
|
|
@ -18,7 +18,7 @@ jobs:
|
|||
coverage:
|
||||
name: cargo llvm-cov
|
||||
if: vars.PUBLIC_FORGE != 'true'
|
||||
runs-on: [hive-ci]
|
||||
runs-on: ${{ vars.PUBLIC_FORGE == 'true' && 'nixos' || 'hive-ci' }}
|
||||
# Above the 30 min `nix flake check` allows, because instrumented
|
||||
# builds are slower than the ordinary ones and this starts from a
|
||||
# cache that the normal jobs never populate.
|
||||
|
|
|
|||
Loading…
Reference in a new issue