ci(release-schedule): trigger from the cluster, not GitHub's cron - #858
Open
funkypenguin wants to merge 1 commit into
Open
ci(release-schedule): trigger from the cluster, not GitHub's cron#858funkypenguin wants to merge 1 commit into
funkypenguin wants to merge 1 commit into
Conversation
GitHub deprioritises scheduled workflows and silently drops ticks: over one 17-hour sample this workflow's own "30 * * * *" cron fired 12 times instead of 17, with gaps up to 2h18m. harbor-themes-v0.11.5 was tagged upstream at 05:19 and the matrix had last run at 04:14, so the image sat unbuilt with nothing reporting a failure. Replaced by a k8s CronJob in infra (cronjobs/dispatch-containers-release--flux-system) that fires workflow_dispatch hourly at :30, matching the cadence this file used to declare. Same pattern as elfhosted/myprecious' release-please workflow. Also adds workflow-level concurrency. A full matrix build routinely outlives the dispatch interval, and because fetch.sh compares against PUBLISHED tags an overlapping run re-derives the same not-yet-pushed changes, so both runs race to push the same tag at different digests. Queueing was previously masked by the dropped ticks; with a reliable trigger it would not be. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
funkypenguin
marked this pull request as ready for review
August 27, 2026 07:05
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
1 participant
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.
Why
GitHub deprioritises scheduled workflows and silently drops ticks. Over one 17-hour sample this workflow's
"30 * * * *"cron fired 12 times instead of 17, with gaps up to 2h18m:harbor-themes-v0.11.5was tagged upstream at 05:19 UTC on 2026-08-27; the matrix had last run at 04:14. The image sat unbuilt for over two hours with nothing reporting a failure —fetch.shhad correctly seen no change on its last run, and the next run never came.Replaced by a k8s CronJob in infra (
cronjobs/dispatch-containers-release--flux-system) firingworkflow_dispatchhourly at :30, the same cadence this file used to declare. Same patternelfhosted/myprecious' release-please workflow already uses.Also: workflow-level concurrency
A full matrix build routinely outlives the dispatch interval. Because
fetch.shcompares against published tags, an overlapping run re-derives the same not-yet-pushed changes, and both runs race to push the same tag at different digests — churning renovate PRs and tenant clusters.That was previously masked by the dropped ticks. With a reliable hourly trigger it would not be.
cancel-in-progress: falselets a running build finish; GitHub keeps at most one pending run, whose matrix is generated fresh when it starts.🤖 Generated with Claude Code