Onboard SonarQube to DevOps Change Velocity — Classic

  • Release version: Washingtondc
  • Updated August 1, 2024
  • 1 minute to read

    • Connect to your Sonar instance to retrieve scan results.

    Before you begin

    Role required: sn_devops.admin or sn_devops.tool_owner

    Procedure

    1. Navigate to All > DevOps > Tools > Create New (legacy).
    2. In the Create DevOps tool form, enter the tool details:
      Tool name Name for the tool you're integrating.
      Tool integration Tool to integrate. Select SonarQube.
      Tool URL SonarQube/SonarCloud instance URL.

      For example,https://sonarcloud.io

      Note:
      Don’t enter the slash (/) character at the end of your Sonar tool URL.
      Tool password / Access token SonarQube user token
      Note:
      Only user tokens generated from User > My Account > Security in your Sonar instance are supported.

      Before generating the token for a SonarQube user, ensure that you grant Browse permission for all your Sonar projects.

      api: Grants complete read/write access to the API, including all groups and projects, the container registry, and the package registry.
      Use MID Server MID Server is optional. Select MID Server for an on-premises tool that is attached to a MID Server. The Application value is automatically set to DevOps and the Capability value is set to REST. For more information, see MID Server selection.
    3. Click Submit to connect to your Sonar instance.
    On successful tool creation, you're taken to the tool record page.
    1. If you want to control access to the tool, add the groups that must be given access to the tool in the Maintained by field on the Access tab.
      The tasks the users in the groups can perform depends on the roles assigned to them.
      • DevOps Tool Owner role: Can view and edit the tool.
      • DevOps App Owner role: Can view the tool and can associate, discover, import historical data, and modify pipeline steps (if applicable) of the tool's objects (such as plans, repositories, and pipelines).
      • DevOps Administrator role: Can edit all tools.
      • Other DevOps roles: Can view the tool.
      Note:
      Only groups containing users with DevOps roles are available for selection in the Maintained by field.

      The All App Owners can view and associate tool objects to applications option becomes available for selection if you choose to restrict access to the tool. This option enables all users having the DevOps App Owner role to access the tool. If selected, they’ll be able to view, associate, discover, import historical data, and modify pipeline steps (if applicable) of the tool's objects.

    What to do next