Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-43417

Sonar Badge does not show proper analysis URL

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Minor
    • Resolution: Unresolved
    • Component/s: sonar-plugin
    • Labels:
    • Environment:
      Jenkins 2.32.2, SonarQube Scanner for Jenkins 2.5, Oracle linux 6.5, Jdk 1.8.0_66, running Jenkins directly
    • Similar Issues:

      Description

      Jenkins Master and SonarQube Slave (Scanner and Server) - ssh slave.

      Context:

      • Pipeline job that is being used as a generic build pipeline for many gitlab repositories.
      • Using dir(${repository_name}) to allocate a subfolder in the workspace with the name of the repo.

      When running two concurrent builds for different projects, one project gets allocated in:
      workspace/MSW-generic-AXIS2-pipeline–RELEASE/gitlabprojectX/
      and the second project gets allocated in:
      workspace/MSW-generic-AXIS2-pipeline–RELEASE@2/gitlabprojectY/

      Scanner goes fine: .sonar folder where it should be for each workspace with the proper information. BUT, the build sonar badge in job history shows in both cases the url scanner for gitlabprojectX (when gitlabprojectY should show its own)

        Attachments

          Activity

          There are no comments yet on this issue.

            People

            Assignee:
            sonarteam Sonar Team
            Reporter:
            xoue Guillermo Solla
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated: