Skip to content

XRAY-159000 - Link the build scan job summary violations to the scanned build - #868

Draft
Jordanh1996 wants to merge 1 commit into
jfrog:devfrom
Jordanh1996:XRAY-159000-build-scan-violations-link
Draft

XRAY-159000 - Link the build scan job summary violations to the scanned build#868
Jordanh1996 wants to merge 1 commit into
jfrog:devfrom
Jordanh1996:XRAY-159000-build-scan-violations-link

Conversation

@Jordanh1996

@Jordanh1996 Jordanh1996 commented Aug 31, 2026

Copy link
Copy Markdown
Contributor

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 inside parseScaVulnerabilities, which the convertor gates behind IncludeVulnerabilities, so violations never got it and getJfrogUrl fell back to the generic ui/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

TestScaScanReference covers 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.


  • The pull request is targeting the dev branch.
  • The code has been validated to compile successfully by running go vet ./....
  • The code has been formatted properly using go fmt ./....
  • All static analysis checks passed.
  • All tests have passed. If this feature is not already covered by the tests, new tests have been added.
  • Updated the Contributing page / ReadMe page / CI Workflow files if needed.
  • All changes are detailed at the description. if not already covered at JFrog Documentation, new documentation have been added.

…ed build

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@Jordanh1996
Jordanh1996 force-pushed the XRAY-159000-build-scan-violations-link branch from 97758cb to c2f1633 Compare August 31, 2026 14:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant