MLE-31921 Scan latest tag in Black Duck - #470
Merged
Merged
Conversation
…ent code location
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the Jenkins pipeline’s Black Duck trigger to scan a rolling latest-<major> image tag so Black Duck results are updated in-place instead of accumulating per-build/per-version code locations.
Changes:
- Updated
scanWithBlackDuck()to submit${dockerRegistry}/${latestTag}to the downstream Black Duck job instead of the versioned${publishImage}tag. - Added inline documentation clarifying the intent to scan a rolling tag.
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
pengzhouml
approved these changes
Aug 16, 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.
Description
Currently this pipeline sends dated tags to BlackDuck which are unique and remain under the branch indefinitely. This means that BlackDuck will keep old vulnerabilities under a version/branch until the scan is deleted.
Checklist:
Owner:
JIRA_ID as part of branch/PR name
Rebase the branch with upstream
Squashed all commits into a single commit
Added Tests
Reviewer:
Reviewed Tests
Added to Release Wiki/Jira