Support deployment to separate gcp project #134
Draft
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
The file ending helps with syntax highlighting #122: Deploy to separate GCP project
This will allow specifying where to push the images right from semaphore #122: Deploy to separate GCP project
The GCP project was hardcoded, but now it's possible to specify a different one using environment variables. #122: Deploy to separate GCP project
All tasks will need the repo #122: Deploy to separate GCP project
Sometimes we just want to check if the build is working or to force a new one #122: Deploy to separate GCP project
New env vars were introduced for deploying and building. These are now in SemaphoreCI #122: Deploy to separate GCP project
#122: Deploy to separate GCP project
MichaelAkvo
force-pushed
the
isco-122-deploy-to-separate-gcp-project
branch
2 times, most recently
from
805c8d4
to
23d2ed1
Compare
MichaelAkvo
force-pushed
the
isco-122-deploy-to-separate-gcp-project
branch
from
23d2ed1
to
1edd439
Compare
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 PR will support deploying ISCO to its own, separate GCP project.
A test is up under https://isco-project.akvotest.org
The major change will be in how a deployment is done to production: via the semaphore CI interface by the click of a button.
It won't be necessary to tag the release anymore. That however can be introduced, which gives us the option to protect the tag and only allow certain members to push the tag. The promotion to production will the start automatically after the tag has been pushed.
Closes #122