CASMTRIAGE-5738 to release/1.5 #2600
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
atifsyedali
changed the title
johren-hpe
reviewed
Jul 24, 2023
johren-hpe
suggested changes
Jul 24, 2023
|
I kicked the build and it succeeded with the fixed docker image. |
johren-hpe
approved these changes
Jul 25, 2023
dzou-hpe
approved these changes
Jul 25, 2023
gbaker-hpe
approved these changes
Jul 25, 2023
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.
Summary and Scope
We reverted our use of
csm-latesttag for iuf-containers image because csm-latest tag was having cache issues local a machine.After we switched back to using hard-coded version tags, it turns out we were still configuring the infrastructure to use csm-latest. This caused some problems. This PR completely removes csm-latest tag for iuf from CSM.
Is this change backwards incompatible, backwards compatible, or a backwards compatible bugfix?
Yes
Issues and Related PRs
List and characterize relationship to Jira/Github issues and other pull requests. Be sure to list dependencies.
Testing
Tested on:
Not tested yet. Will be tested as part of CSM install
Risks and Mitigations
Are there known issues with these changes? Any other special considerations?
No
Pull Request Checklist