Skip to main content

Check out Port for yourself ➜ 

SonarQube

Loading version...

Port's SonarQube integration allows you to model SonarQube resources in your software catalog and ingest data into them.

Supported resources ProjectIssueSaas AnalysisOn-Premises AnalysisPortfolio

Setup​

Choose your preferred installation method below. Not sure which to pick? See the installation methods overview.

Configuration​

Port integrations use a YAML mapping block to ingest data from the third-party api into Port.

The mapping makes use of the JQ JSON processor to select, modify, concatenate, transform and perform other operations on existing fields and values from the integration API.

Default mapping configuration​

This is the default mapping configuration for this integration:

Default mapping configuration (click to expand)
deleteDependentEntities: true
createMissingRelatedEntities: true
enableMergeEntity: true
resources:
- kind: projects_ga
  selector:
    query: 'true'
    apiFilters:
      qualifier:
      - TRK
    metrics:
    - code_smells
    - coverage
    - bugs
    - vulnerabilities
    - duplicated_files
    - security_hotspots
    - new_violations
    - new_coverage
    - new_duplicated_lines_density
  port:
    entity:
      mappings:
        identifier: .key
        title: .name
        blueprint: '"sonarQubeProject"'
        properties:
          organization: .organization
          link: .__link
          qualityGateStatus: .__branch.status.qualityGateStatus
          lastAnalysisDate: .analysisDate
          numberOfBugs: .__measures[]? | select(.metric == "bugs") | .value
          numberOfCodeSmells: .__measures[]? | select(.metric == "code_smells") | .value
          numberOfVulnerabilities: .__measures[]? | select(.metric == "vulnerabilities") | .value
          numberOfHotSpots: .__measures[]? | select(.metric == "security_hotspots") | .value
          numberOfDuplications: .__measures[]? | select(.metric == "duplicated_files") | .value
          coverage: .__measures[]? | select(.metric == "coverage") | .value
          mainBranch: .__branch.name
          revision: .revision
          managed: .managed
        relations:
          group: '"all_teams"'
- kind: issues
  selector:
    query: 'true'
    apiFilters:
      resolved: 'false'
    projectApiFilters: {}
  port:
    entity:
      mappings:
        identifier: .key
        title: .message
        blueprint: '"sonarQubeIssue"'
        properties:
          type: .type
          severity: .severity
          link: .__link
          status: .status
          assignees: .assignee
          tags: .tags
          createdAt: .creationDate
        relations:
          sonarQubeProject: .project

Mapping & examples per resource​

Use the explorer below to view sample payloads and the resulting Port entities for each resource type. For additional resources and advanced configurations, see the examples page.

Monitoring and sync status​

To learn more about how to monitor and check the sync status of your integration, see the relevant documentation.

Examples​

To view and test the integration's mapping against examples of the third-party API responses, use the jq playground in your data sources page. Find the integration in the list of data sources and click on it to open the playground.

Examples of blueprints and the relevant integration configurations can be found on the sonarqube examples page