XRAY-159000 - Link the build scan job summary violations to the scanned build - #868
Draft
Jordanh1996 wants to merge 1 commit into
Draft
XRAY-159000 - Link the build scan job summary violations to the scanned build#868Jordanh1996 wants to merge 1 commit into
Jordanh1996 wants to merge 1 commit into
Conversation
…ed build Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Jordanh1996
force-pushed
the
XRAY-159000-build-scan-violations-link
branch
from
August 31, 2026 14:39
97758cb to
c2f1633
Compare
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.
https://jfrog-int.atlassian.net/browse/XRAY-159000
Background
In the job summary of a published build, the table shows "Security Violations" and "Security Issues", each linking "See the results of the scan in JFrog". The Issues link opens that build's scan results; the Violations link opens the unfiltered list of every build scan on the platform, so users have to search for their own build by hand.
Description
Xray returns the link to the scan results (
more_details_url) on the SCA scan response. It was copied to the summary insideparseScaVulnerabilities, which the convertor gates behindIncludeVulnerabilities, so violations never got it andgetJfrogUrlfell back to the genericui/scans-list/builds-scans. The job summary now attaches it to every issue type of the scan, next to the target names adjustment it already does (a violations only run,jf build-scan --violations, never reaches the vulnerabilities parsing at all, so the reference has to be read outside of it).Tests
TestScaScanReferencecovers both modes. Live e2e on a SaaS platform:jf mvn->jf rt build-publish->jf build-scan->jf gsm, with and without--vuln; both cells deep-link to the scanned build.devbranch.go vet ./....go fmt ./....