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

SonarQube's sonar.ProjectBaseDir Set to the first module on the list

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • sonar-plugin
    • Windows Server 2008

      VERSION:
      Jenkins 1.573
      Subversion Plugin 2.4.1
      Sonar Plugin 2.1

      When using multiple SVN Url's in one project, with each set to the following:

      Repository URL: http://svnserver/repo/Project/module1/trunk/src
      Local Module Directory: module1

      Repository URL: http://svnserver/repo/Project/module2/trunk/src
      Local Module Directory: module2

      ...

      My sonar.ProjectBaseDir is being set improperly, causing builds to fail. Where the property in this case should be set to C:\Jenkins\Jobs\Project\Workspace , it is instead being set to C:\Jenkins\Jobs\Project\Workspace\module1

      When trying to set the property manually with
      sonar.ProjectBaseDir=$WORKSPACE
      it comes out as -Dsonar.projectBaseDir=D:JenkinsjobsProjectNameworkspace (No slashes)

      Any attempts to backreference sonar properties to the workspace parent folder have proven unsuccessful

          [JENKINS-24044] SonarQube's sonar.ProjectBaseDir Set to the first module on the list

          Shawn Cole created issue -
          Shawn Cole made changes -
          Description Original: When using multiple SVN Url's in one project, with each set to the following:

          Repository URL: http://svnserver/repo/Project/module1/trunk/src
          Local Module Directory: module1

          Repository URL: http://svnserver/repo/Project/module2/trunk/src
          Local Module Directory: module2

          ...

          $WORKSPACE in this case is set to C:\Jenkins\Jobs\Project\Workspace.
          Instead, workspace is being set to C:\Jenkins\Jobs\Project\Workspace\module1.

          Not having the working directory set correctly is a big issue for my downstream steps.
          New: When using multiple SVN Url's in one project, with each set to the following:

          Repository URL: http://svnserver/repo/Project/module1/trunk/src
          Local Module Directory: module1

          Repository URL: http://svnserver/repo/Project/module2/trunk/src
          Local Module Directory: module2

          ...

          $WORKSPACE in this case Should Be set to C:\Jenkins\Jobs\Project\Workspace.
          Instead, workspace is being set to C:\Jenkins\Jobs\Project\Workspace\module1.

          Not having the working directory set correctly is a big issue for my downstream steps.

          Daniel Beck added a comment -

          Reducing priority as this does not result in crash or data loss, and seems to have an easy workaround in using the parent directory of the provided WORKSPACE.

          Please provide a sample job config.xml file.

          Please specify the version of Jenkins and Subversion plugin (we're not using the Jira version fields).

          Daniel Beck added a comment - Reducing priority as this does not result in crash or data loss, and seems to have an easy workaround in using the parent directory of the provided WORKSPACE. Please provide a sample job config.xml file. Please specify the version of Jenkins and Subversion plugin (we're not using the Jira version fields).
          Daniel Beck made changes -
          Priority Original: Critical [ 2 ] New: Minor [ 4 ]
          Shawn Cole made changes -
          Attachment New: config.xml [ 26460 ]
          Description Original: When using multiple SVN Url's in one project, with each set to the following:

          Repository URL: http://svnserver/repo/Project/module1/trunk/src
          Local Module Directory: module1

          Repository URL: http://svnserver/repo/Project/module2/trunk/src
          Local Module Directory: module2

          ...

          $WORKSPACE in this case Should Be set to C:\Jenkins\Jobs\Project\Workspace.
          Instead, workspace is being set to C:\Jenkins\Jobs\Project\Workspace\module1.

          Not having the working directory set correctly is a big issue for my downstream steps.
          New: VERSION:
          Jenkins 1.573
          Subversion Plugin 2.4.1

          When using multiple SVN Url's in one project, with each set to the following:

          Repository URL: http://svnserver/repo/Project/module1/trunk/src
          Local Module Directory: module1

          Repository URL: http://svnserver/repo/Project/module2/trunk/src
          Local Module Directory: module2

          ...

          $WORKSPACE in this case Should Be set to C:\Jenkins\Jobs\Project\Workspace.
          Instead, workspace is being set to C:\Jenkins\Jobs\Project\Workspace\module1.

          Not having the working directory set correctly is a big issue for my downstream steps.

          Daniel Beck added a comment -

          Cannot reproduce the issue (haven't used your config exactly of course, but still, two locations checked out, both in subdirs, 'echo $WORKSPACE' in the shell...

          Do you have env-inject installed? If so, what version? What happens when you disable it, or could you set up a pristine Jenkins instance and try to reproduce the issue there?

          Daniel Beck added a comment - Cannot reproduce the issue (haven't used your config exactly of course, but still, two locations checked out, both in subdirs, 'echo $WORKSPACE' in the shell... Do you have env-inject installed? If so, what version? What happens when you disable it, or could you set up a pristine Jenkins instance and try to reproduce the issue there?
          Shawn Cole made changes -
          Component/s New: sonar [ 15523 ]
          Description Original: VERSION:
          Jenkins 1.573
          Subversion Plugin 2.4.1

          When using multiple SVN Url's in one project, with each set to the following:

          Repository URL: http://svnserver/repo/Project/module1/trunk/src
          Local Module Directory: module1

          Repository URL: http://svnserver/repo/Project/module2/trunk/src
          Local Module Directory: module2

          ...

          $WORKSPACE in this case Should Be set to C:\Jenkins\Jobs\Project\Workspace.
          Instead, workspace is being set to C:\Jenkins\Jobs\Project\Workspace\module1.

          Not having the working directory set correctly is a big issue for my downstream steps.
          New: VERSION:
          Jenkins 1.573
          Subversion Plugin 2.4.1

          When using multiple SVN Url's in one project, with each set to the following:

          Repository URL: http://svnserver/repo/Project/module1/trunk/src
          Local Module Directory: module1

          Repository URL: http://svnserver/repo/Project/module2/trunk/src
          Local Module Directory: module2

          ...

          My sonar.ProjectBaseDir is being set improperly, causing builds to fail. Where the property in this case should be set to C:\Jenkins\Jobs\Project\Workspace , it is instead being set to C:\Jenkins\Jobs\Project\Workspace\module1
          Shawn Cole made changes -
          Description Original: VERSION:
          Jenkins 1.573
          Subversion Plugin 2.4.1

          When using multiple SVN Url's in one project, with each set to the following:

          Repository URL: http://svnserver/repo/Project/module1/trunk/src
          Local Module Directory: module1

          Repository URL: http://svnserver/repo/Project/module2/trunk/src
          Local Module Directory: module2

          ...

          My sonar.ProjectBaseDir is being set improperly, causing builds to fail. Where the property in this case should be set to C:\Jenkins\Jobs\Project\Workspace , it is instead being set to C:\Jenkins\Jobs\Project\Workspace\module1
          New: VERSION:
          Jenkins 1.573
          Subversion Plugin 2.4.1
          Sonar Plugin 2.1

          When using multiple SVN Url's in one project, with each set to the following:

          Repository URL: http://svnserver/repo/Project/module1/trunk/src
          Local Module Directory: module1

          Repository URL: http://svnserver/repo/Project/module2/trunk/src
          Local Module Directory: module2

          ...

          My sonar.ProjectBaseDir is being set improperly, causing builds to fail. Where the property in this case should be set to C:\Jenkins\Jobs\Project\Workspace , it is instead being set to C:\Jenkins\Jobs\Project\Workspace\module1

          When trying to set the property manually with
          sonar.ProjectBaseDir=$WORKSPACE
          it comes out as -Dsonar.projectBaseDir=D:JenkinsjobsProjectNameworkspace (No slashes)

          Any attempts to backreference sonar properties to the workspace parent folder have proven unsuccessful
          Labels Original: modules scm subversion New: modules scm sonar subversion
          Priority Original: Minor [ 4 ] New: Major [ 3 ]
          Summary Original: WORKSPACE Environment Variable Set to the first module on the list New: SonarQube's sonar.ProjectBaseDir Set to the first module on the list

          Shawn Cole added a comment -

          Sorry Daniel, thanks for your troubleshooting, it seems the problem isn't related the to Workspace Environment Variable, but rather the sonar plugin. The Env-Inject Plugin is not installed on this instance.

          Shawn Cole added a comment - Sorry Daniel, thanks for your troubleshooting, it seems the problem isn't related the to Workspace Environment Variable, but rather the sonar plugin. The Env-Inject Plugin is not installed on this instance.

          Daniel Beck added a comment -

          And you even had echo %WORKSPACE% in there...

          FWIW it's almost sure SCM.getModuleRoot returning the first checked out module directory being used to set Sonar base directory. I observed the same braindead behavior with the Gradle plugin.

          Daniel Beck added a comment - And you even had echo %WORKSPACE% in there... FWIW it's almost sure SCM.getModuleRoot returning the first checked out module directory being used to set Sonar base directory. I observed the same braindead behavior with the Gradle plugin.
          Daniel Beck made changes -
          Component/s Original: subversion [ 15485 ]
          Affects Version/s Original: current [ 10162 ]
          Labels Original: modules scm sonar subversion New: sonar

            Unassigned Unassigned
            cole9350 Shawn Cole
            Votes:
            4 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated: