ci(sync-addons): run hourly instead of daily#210
Closed
rubenhensen wants to merge 1 commit into
Closed
Conversation
So that a new upstream manifest.xml lands on staging within an hour of release instead of waiting up to ~24h for the next cron tick. The script is a cheap no-op when sha256 is unchanged, so the extra runs are effectively free against the 5000/h authenticated API quota.
Contributor
Author
|
Superseded by the container-self-refresh approach (PR coming) — hourly cron is unnecessary once the running container picks up addon releases on its own loop. |
5 tasks
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.
Summary
.github/workflows/sync-addons.ymlcron from0 6 * * *(daily 06:00 UTC) to0 * * * *(hourly at :00 UTC).manifest.xmlreaches thechore/sync-addonsPR within an hour of release instead of waiting for the next 06:00 UTC tick.Why
[outlook] up-to-date: v0.1.3. Upstream then published v0.3.0 at 12:13 UTC with new content (sha256e5b19b19…4d76, 10457 bytes). With daily cron, that won't be picked up until tomorrow morning.GITHUB_TOKENwe're well under the 5000/h authenticated quota.Test plan
chore/sync-addons.