-
Notifications
You must be signed in to change notification settings - Fork 43
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
Run git builds on schedule #1100
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Assuming our staff stick closer to the standard 9-5 most of the time, would running a 2nd CRON job just after 17:00 not be more suitable?
Just curious.
Times seem pretty arbitrary, some comments for why would be good |
I picked the minutes arbitrary, it's considered "good practice" to pick something at random that isn't exactly 0, 15, 30, or 45 because everyone else runs their CI at that time. I picked the hours 08 and 15 because it's before most of our start and end times. The idea is that we'd be able to fix any issues without going into overtime. |
We could technically further limit the schedule to only run on work days. |
Yeah, we should do that. |
Updated to
|
My train of thought was the exact same when I made the suggestion.
I commented, because I thought the end time was actually set too early, rather than too late. |
Fixes #1079. Using
17 08,15 * * *
as a schedule: