Continuous Deployment from master #2605
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
This changes our semaphore config to auto promost the master branch to production for all environments, assuming CI passes and previous workflows have passed. When we move to this sort of continous deployment, it doesn't really make sense to cut tags for every release, because basically every merge ref will become a release. I've kept the logic around deploying tags that start with `release-` for backwards compatiblity, for times when we want to cut releases by hand still.
rsanheim
changed the title
harimohanraj89
approved these changes
Jun 17, 2021
I think keep around for now in case we want to use it for specific special case releases?
Yup I pinged all server-devs in my standup message from yesterday, and from previous discussions I think everyone is on board with giving this a shot. |
|
LGTM. I'm in favor of keeping |
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 changes our semaphore config to auto promost the master branch to
production for all environments, assuming CI passes and previous
workflows have passed.
When we move to this sort of continous deployment, it doesn't really
make sense to cut tags for every release, because basically every merge
ref will become a release.
I've kept the logic around deploying tags that start with
release-forbackwards compatiblity, for times when we want to cut releases by hand
still.
We currently have alerts coming to
#alertsand#botsin Slack as things progress through workflows - do we need anything else for good visibility into this?