Run CI midday Sunday #18
Conversation
Jongmassey
force-pushed
the
Jongmassey/run-CI-weekly
branch
from
15344c4 to
3c363c4
Compare
| @@ -11,6 +11,8 @@ on: | |||
| pull_request: | |||
| push: | |||
| branches: [main] | |||
| schedule: | |||
| - cron: "0 12 * * SUN" | |||
There was a problem hiding this comment.
Midday on Sunday is quiet for us, but not quiet for GitHub:
The
scheduleevent can be delayed during periods of high loads of GitHub Actions workflow runs. High load times include the start of every hour. If the load is sufficiently high enough, some queued jobs may be dropped. To decrease the chance of delay, schedule your workflow to run at a different time of the hour.
As Simon suggested,1 could you change the minute field to something less regular?
Footnotes
Jongmassey
force-pushed
the
Jongmassey/run-CI-weekly
branch
from
0ee9909 to
79933b0
Compare
time chosen as least likely to interrupt users whilst giving plenty of time to complete before Monday avoiding on-the-hour as likely period of high system load
Jongmassey
force-pushed
the
Jongmassey/run-CI-weekly
branch
from
79933b0 to
16b2cf3
Compare
There was a problem hiding this comment.
Thanks, @Jongmassey 👍🏻.
Micro feedback: Avoid description in commits/PRs. The code tells us what changed. Embrace explanation, because knowing why it changed is going to be useful and interesting in the future. Consider the following commit/PR:
Run CI workflow on schedule
The schedule was chosen to avoid high system load, as described by the
[GitHub Actions documentation][1]. It's unlikely to interrupt users.
[1]: https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows#schedule
time chosen as least likely to interrupt users
whilst giving plenty of time to complete before Monday