Dynamic image tagging using PR-specific variables in Azure DevOps pip… #3974
+23
−37
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.
Which issue this PR addresses:
This PR addresses the need for improved image management in the pipeline by introducing PR-specific tagging for RP images. Currently, it can be challenging to trace images back to specific pull requests, which complicates troubleshooting and version management. This update standardizes image tags, supports artifact caching, and enables caching for dependent images, improving both efficiency and traceability.
Fixes: 9503
What this PR does / why we need it:
This PR adds several key enhancements to the CI pipeline:
(pr-${PR_NUMBER}-${GIT_COMMIT_SHA})
. This improves traceability by linking images directly to the pull requests that generated them.Key benefits:
Test plan for issue:
Verify PR-specific tagging
(pr-${PR_NUMBER}-${GIT_COMMIT_SHA})
in dev ACR, confirm artifact caching reuses previous buildsIs there any documentation that needs to be updated for this PR?
N/A
How do you know this will function as expected in production?
N/A