Change the schedule of GA crons #1576
Merged
Conversation
This file contains 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
…(5AM PST & 8AM EST) This is a better schedule because it runs right before people start working in our team hence giving us a chance to quickly respond to failures, also doesn't take the computing capacity when we need it (during working hours). Finally this will capture more changes than before because there's a chance the code gets updated after hours.
✅ Deploy Preview for karpenter-docs-prod canceled.
|
ellistarn
approved these changes
Mar 25, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
1. Issue, if available:
Changes the schedule so that both actions run every day at 12:00 UTC (5AM PST & 8AM EST) this is a better schedule because it runs right before people start working in our team hence giving us a chance to quickly respond to failures, also doesn't take the computing capacity when we need it (during working hours). Finally this will capture more changes than before because
there's a chance the code gets updated after hours.
2. Description of changes:
3. How was this change tested?
4. Does this change impact docs?
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.