Skip to content

feat(ci): add a dry_run input to rehearse the release pipeline - #32

Open
danceratopz wants to merge 1 commit into
spencer-tb:ci/nightly-fillfrom
danceratopz:ci/nightly-dry-run
Open

feat(ci): add a dry_run input to rehearse the release pipeline#32
danceratopz wants to merge 1 commit into
spencer-tb:ci/nightly-fillfrom
danceratopz:ci/nightly-dry-run

Conversation

@danceratopz

Copy link
Copy Markdown

🗒️ Description

The schedule path keys entirely on github.event_name == 'schedule' and cannot run in PR CI, so the first real execution of the merged nightly behavior would be the 02:00 cron itself. This adds a dry_run boolean dispatch input that follows the same no-release path from the Actions UI: the release job is skipped (no tag, no draft), fail-fast is off so every fork range reports, nightly artifact retention applies, and the run queues in the nightly-fill concurrency group. Dry runs are dispatch events, so the nightly baseline in check_new_commits.py (filtered on event=schedule) never counts them, and #31's promotion can never select their artifacts. Composes with any feature, so benchmark and devnet releases can be rehearsed end-to-end too.

🔗 Related Issues or PRs

Targets the head branch of ethereum#3100; complements #31.

✅ Checklist

  • All: Ran fast static checks to avoid unnecessary CI fails, see also Code Standards and Verifying Changes:
    just static
  • All: PR title have the form <type>(<area>):, where <type> and <area> come from an approrpriate C-<type>, respectively A-<area>, label. The title should match the a target squash commit message.
  • All: Considered updating the online docs in the ./docs/ directory.

Cute Animal Picture

just a rehearsal

Everything schedule-specific in the release workflow keys on
`github.event_name == 'schedule'`, which cannot be triggered by hand,
and the cron path cannot run in PR CI, so the first real execution of
the nightly behavior would be the 02:00 run itself.

Add a `dry_run` boolean dispatch input that follows the same
no-release path for any feature: the `release` job is skipped (no
tag, no draft), `fail-fast` is disabled so every fork range reports,
nightly artifact retention applies and the run queues in the
`nightly-fill` concurrency group. Dry runs are dispatch events, so
the nightly baseline in `check_new_commits.py` (filtered on
`event=schedule`) never counts them.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant