Skip to content

chore: Change cron schedule for ISO upload to monthly#57

Merged
inffy merged 2 commits into
mainfrom
iso-schedule
May 13, 2026
Merged

chore: Change cron schedule for ISO upload to monthly#57
inffy merged 2 commits into
mainfrom
iso-schedule

Conversation

@inffy
Copy link
Copy Markdown
Member

@inffy inffy commented May 12, 2026

No need to build these every week

Copilot AI review requested due to automatic review settings May 12, 2026 07:58
@inffy inffy requested review from NiHaiden, ledif and renner0e as code owners May 12, 2026 07:58
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the GitHub Actions workflow schedule for building/uploading stable ISOs so it runs monthly instead of weekly, reducing unnecessary recurring builds.

Changes:

  • Changed the schedule cron trigger from weekly (Wednesdays) to monthly (5th day of the month) at 03:00 UTC.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@codacy-production
Copy link
Copy Markdown

codacy-production Bot commented May 12, 2026

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.

renner0e
renner0e previously approved these changes May 12, 2026
Copy link
Copy Markdown
Member

@renner0e renner0e left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

SGTM, maybe it would make sense to do this on the first monday of the month, so we get an old (6d) tested image instead or right after the stable images published of that week

@inffy
Copy link
Copy Markdown
Member Author

inffy commented May 12, 2026

SGTM, maybe it would make sense to do this on the first monday of the month, so we get an old (6d) tested image instead or right after the stable images published of that week

That would need some kind of check then in the beginning of the job. Don't think we can do that just with cron or can we?`

These would go to the testing bucket anyway first so I was thinking we could just do a quick test on VM that it works and then promote it? We can easily change the day to the first of the month

@renner0e
Copy link
Copy Markdown
Member

SGTM, maybe it would make sense to do this on the first monday of the month, so we get an old (6d) tested image instead or right after the stable images published of that week

That would need some kind of check then in the beginning of the job. Don't think we can do that just with cron or can we?`

These would go to the testing bucket anyway first so I was thinking we could just do a quick test on VM that it works and then promote it? We can easily change the day to the first of the month

Yeah it's not super important anyway, but yeah definitely keep the manual promotion

@inffy inffy merged commit aea6ec9 into main May 13, 2026
3 checks passed
@inffy inffy deleted the iso-schedule branch May 13, 2026 06:01
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.

3 participants