Test/deploy bbm #5
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
For now, pushes in DEV will trigger the creation of a dev_ tag. The workflow is not covering the replacement of the production tag because this should be a manual operation a few weeks/months after migration. To be more precise, we should automate this flow after we bump buildbot version.
When master container is under development we must ensure that configuration changes are valid on both buildbot master versions, PROD/DEV. Let's say one will bring a new feature to Production independently of a master upgrade.
- no automation for now, only copy the configuration files, prepare docker-compose and Autogen/ masters - will work only on manual dispatch from the Main branch - renamed secrets for better env classification
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.
No description provided.