Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add weekly scheduled run to make sure that CI stays green. #695

Merged
merged 1 commit into from
May 26, 2023

Conversation

nuclearsandwich
Copy link
Contributor

@nuclearsandwich nuclearsandwich commented Mar 4, 2023

In order to keep track of regressions due to drift / bitrot versus regressions introduced by new PRs.

Answering the question of why 7:40 UTC on Sundays which was raised by @ijnek:

Why 7?

The clock for scheduled actions in GitHub Actions uses UTC so 07:40 UTC is 11:40 / 00:40 US Pacific which means.

Why 40?

Kind of no reason. GitHub Actions lacks the cron syntax extension for picking a single random value within the field (something Jenkins does with its H value) in order to spread scheduled build load out across the hour. 0 and 30 are the most commonly used times so I just shifted slightly from that.

Why Sunday?

It's the first night of the workweek which means that we can show up Monday morning and see whether the previous week brought any new issues to CI. In terms of vague "workweek" notions the objective of this build is to catch the "last" regressions of the previous week's changes rather than the "first" regressions of the coming week.

Of course, for people in UTC+ timezones this job starts in the middle of their Monday so this is a US-biased notion.

@ijnek
Copy link
Member

ijnek commented Mar 6, 2023

Out of interest - why 7.40 on Sunday?

@nuclearsandwich
Copy link
Contributor Author

Out of interest - why 7.40 on Sunday?

A perfectly valid question and one I should have explained in the PR description. Thanks for raising it!

Why 7?

The clock for scheduled actions in GitHub Actions uses UTC so 07:40 UTC is 11:40 / 00:40 US Pacific which means.

Why 40?

Kind of no reason. GitHub Actions lacks the cron syntax extension for picking a single random value within the field (something Jenkins does with its H value) in order to spread scheduled build load out across the hour. 0 and 30 are the most commonly used times so I just shifted slightly from that.

Why Sunday?

It's the first night of the workweek which means that we can show up Monday morning and see whether the previous week brought any new issues to CI. In terms of vague "workweek" notions the objective of this build is to catch the "last" regressions of the previous week's changes rather than the "first" regressions of the coming week.

Of course, for people in UTC+ timezones this job starts in the middle of their Monday so this is a US-biased notion.

@ijnek
Copy link
Member

ijnek commented Mar 7, 2023

Got it - thanks for the explanation!

@nuclearsandwich nuclearsandwich merged commit d3d21ae into master May 26, 2023
@nuclearsandwich nuclearsandwich deleted the scheduled-ci branch May 26, 2023 22:48
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