ci: add scheduled dispatcher for stable branch tests#792
Merged
Conversation
GitHub only fires schedule: triggers on the default branch, so squid (and future stable branches) get no periodic CI signal for the CI health dashboard's flaky-rate calculation. Add a dispatcher on main that runs tests.yml on squid daily via workflow_dispatch, which is exempt from the Actions recursion guard under GITHUB_TOKEN. Assisted-by: claude-code:claude-sonnet-5 Signed-off-by: John Ramsden <john.ramsden@canonical.com>
f5911d9 to
587ade9
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
GitHub only fires
schedule:triggers on the default branch, sosquid(and any future stable branch) gets no periodic CI signal — the CI health dashboard's CE144 flaky-rate calculation counts onlypush/schedule/workflow_dispatchruns, andsquidsaw just 2 pushes in the last 60 days, so it usually shows "no data".Adds
.github/workflows/scheduled-branch-tests.yml: runs Mon/Thu 02:00 UTC (plus manual dispatch), fanning outgh workflow run tests.yml --ref <branch>per entry in a matrix (currently justsquid; add future stable branches to the matrix as needed).workflow_dispatchevents triggered via the defaultGITHUB_TOKENare exempt from the Actions recursion guard, so no PAT is required — onlypermissions: actions: write.Depends on #791 — that PR adds the
workflow_dispatchtrigger tosquid'stests.yml; dispatch from this workflow will fail with "workflow does not have a workflow_dispatch trigger" until it merges.Type of change
How has this been tested?
After both PRs merge:
gh workflow run scheduled-branch-tests.yml --repo canonical/microceph --ref mainshould spawn a Tests run onsquid. Confirmed via:No dashboard config changes needed — it already monitors both
mainandsquid.Contributor checklist