Add scheduled RC deploys #1658
Merged
Add scheduled RC deploys #1658
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
This deploys the latest `production` build on `main` to one of our test canisters, every Tuesday evening (Zurich time). This works by fetching all `production` build artifacts on the `main` branch and grabbing the latest one; then it reuses the infrastructure we have in place to deploy to mainnet test canisters. Finally, a message is sent to our private slack.
frederikrothenberger
approved these changes
Jun 1, 2023
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.
This deploys the latest
productionbuild onmainto one of our test canisters, every Tuesday evening (Zurich time).This works by fetching all
productionbuild artifacts on themainbranch and grabbing the latest one; then it reuses the infrastructure we have in place to deploy to mainnet test canisters.Finally, a message is sent to our private slack.
Some of this (fetching artifacts, deploying) can be extracted into separate actions. We can do this when the need arises.