JFrog Evidence Collection

Understanding the SonarQube Cloud integration with JFrog Evidence Collection.

This integration requires the SonarQube Cloud Enterprise license.

circle-check

The JFrog Evidence Collectionarrow-up-right expands JFrog’s Release Lifecycle Management capabilities to enrich artifacts, builds, and release bundles with signed attestation metadata that can be easily tracked and verified for governance and compliance.

Prerequisites

  • SonarQube Cloud Enterprise license

  • JFrog Artifactory Enterprise+ license

  • Minimum JFrog CLI version: 2.78.9

Integration overview

The JFrog CLIarrow-up-right is used within the CI pipeline to create the Sonar evidence that will be displayed on the JFrog platform. This evidence contains the quality gate status computed by SonarQube Cloud and made accessible via its API.

The figure below shows the process:

  1. The CI pipeline starts the SonarQube analysis.

  2. The SonarScanner performs the analysis and sends the results to SonarQube Cloud.

  3. SonarQube Cloud processes the analysis results and computes the quality gate status.

  4. The CI pipeline asks JFrog CLI to create the Sonar evidence for the analysis.

  5. The JFrog CLI, which waits for the analysis completion, retrieves SonarQube analysis evidence payload from SonarQube Cloud's endpoint: api.sonarcloud.io/dop-translation/jfrog-evidencearrow-up-right (see JFrog Evidence Collection below).

The JFrog CLI waits for the SonarQube Cloud analysis completion, retrieves SonarQube analysis evidence payload from SonarQube Cloud's endpoint, creates the Sonar evidence, and sends it to JFrog Evidence Collection.

Example of a Sonar endpoint response

The endpoint response contains the evidence payload in JSON format with a markdown section.

Last updated

Was this helpful?