Update RC tagging and test process flow to ensure RC testing is proper #179
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
RC testing process which we have now builds and RC image based on last released openshift version Ex. 4.17.1.rc will be actually testing 4.16.0 helm image. This flow is not correct. We missed to see a production issue in rc testing due to this. So, we are now certifying an rc build first, then update the image in this repo before proceeding with local testing. This ensures rc build which we test is similar to production build and helps us capture in rc testing.
Gourav2906
approved these changes
Nov 28, 2025
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.
RC testing process which we have now builds and RC image based on last released openshift version Ex. 4.17.1.rc will be actually testing 4.16.0 helm image.
This flow is not correct.
We missed to see a production issue in rc testing due to this.
So, we are now certifying an rc build first, then update the image in this repo before proceeding with local testing.
This ensures rc build which we test is similar to production build and helps us capture in rc testing.