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

Move days of unstable runs #213

Merged
merged 1 commit into from
Jul 15, 2022
Merged

Move days of unstable runs #213

merged 1 commit into from
Jul 15, 2022

Conversation

amanda11
Copy link
Contributor

Changing days of builds as follows (times based on US/Pacific):

  • Tues @ 18:00 Orphan run (cicd repo)
  • Wed @ 6:00 Stable run (cd repo - no change)
  • Wed @ 8:00 Unstable run (ci repo)
  • Wed @ 18:00 Orphan run (cicd repo)
  • Thur @ 8:00 Unstable run (ci repo)
  • Thur @ 18:00 Orphan run (cicd repo)

If this runs ok, then propose that we have AWS Lambda control the EC2 instance with:

  • Start Tues@16:00
  • Stop Thurs@20:00
    Therefore reducing to 52 hrs a week instead of 168.

This then means each week we still have 2 unstable, and 1 stable. We have orphan run after each day of running CIs but also at startup - in case of any problems previous week. Should enable servers to be up long enough to debug any problems.

@amanda11 amanda11 merged commit 5dca804 into master Jul 15, 2022
@amanda11 amanda11 deleted the move_unstable branch July 15, 2022 09:15
@amanda11
Copy link
Contributor Author

Part of StackStorm/community#104

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.

2 participants