CAS-1263 - Implement rolling deployments for the API service #1149
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
NToppingCCS
approved these changes
Apr 25, 2023
tim-s-ccs
force-pushed
the
feature/CAS-1263-deploy-with-travis
branch
3 times, most recently
from
19295b6
to
4e7befc
Compare
tim-s-ccs
force-pushed
the
feature/CAS-1263-deploy-with-travis
branch
2 times, most recently
from
13dca89
to
aae7c78
Compare
…es the CloudFoundry deployment provider to deploy the applications to the various environments. What’s more, I have enabled rolling deployments so there is no downtime when we do deployments. Importantly, this means that if the new code won’t deploy, we will not take down the existing code deployment (which is what currently happens). Now that we don’t use terraform for deployments, this code can (or should) be moved to a separate repository that looks after the CAS infrastructure. Note, I would have preferred to have written the deployment script once and then use some conditional logic to determine which environment to deploy to. However, as not all deployments are linked to static branches, I have had to split the deployment parts up to manage the releases to Sandbox (2 and 3).
tim-s-ccs
force-pushed
the
feature/CAS-1263-deploy-with-travis
branch
from
aae7c78
to
f82d5da
Compare
|
Code Climate has analyzed commit f82d5da and detected 0 issues on this pull request. View more on Code Climate. |
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.
JIRA link (if applicable)
CAS-1263
Change description
As part of this commit I have updated the Travis config so that it uses the CloudFoundry deployment provider to deploy the applications to the various environments. What’s more, I have enabled rolling deployments so there is no downtime when we do deployments. Importantly, this means that if the new code won’t deploy, we will not take down the existing code deployment (which is what currently happens).
Now that we don’t use terraform for deployments, this code can (or should) be moved to a separate repository that looks after the CAS infrastructure.
Note, I would have preferred to have written the deployment script once and then use some conditional logic to determine which environment to deploy to. However, as not all deployments are linked to static branches, I have had to split the deployment parts up to manage the releases to Sandbox (2 and 3).
Does this PR introduce a breaking change?
Before creating a pull request make sure that: