DRAFT: Feat/add stagingimage hub to pipeline #13
+15
−15
Conversation
This file contains hidden or 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
If you target an environment like you do, then you already have either prod or dev secrests/variables |
|
How can we manually deploy from a PR? Create a temporary tag which harbor recognizes as higher prio than latest? |
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.
As an MVP, i want to be able to always push a build to the second staging server. In later configurations, the right way to go (in my opinion) would be to have DEV, or PROD prefix for the secrets. all merge request pipelines manually go to staging. All development branch pipelines automatically go to staging. All ma[in/ster] pipelines go to prod. Just a ctrl c+v of the pipeline, arguably in n different files (dev.yml and prod.yml, or MR.yml, development.yaml, main.yaml, etc.)