SRS-1642 DevOps Test Setup - #558
Merged
Merged
Conversation
- Create configuration for test namespace - Create image promotion pipelines - Remove automatic helm deploys on merge to dev - Update documentation
- add namespaces - make pipelines more resilient
bolny
force-pushed
the
bolny/srs_1642_test_env_setup
branch
from
June 30, 2026 21:06
79b506b to
a2f0bf3
Compare
bolny
force-pushed
the
bolny/srs_1642_test_env_setup
branch
from
June 30, 2026 21:23
08b5584 to
0011eb0
Compare
nupurdixit13
reviewed
Jul 8, 2026
bolny
commented
Jul 8, 2026
nupurdixit13
approved these changes
Jul 8, 2026
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
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.
I will issue a follow up PR to document the learning and modified code from our experimental run on re-initializing the database.
This is mostly identical to the setup used in the dev namespace. The only difference, other than the namespace, is that it does not rely on images built from GitHub sources, it triggers rollouts when our ImageStreams in the tools namespace get a new image with the
testtag. There is an included pipeline that will execute the correct commands.