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

Sonar runner plugin doesn't let you control execution directory, problem if you need proejct base to be top level

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • sonar-plugin
    • None

      I have a project that checks out into $WORKSPACE/projectname, generates reports to $WORKSPACE/reports/coverage.xml, and the coverage reports contain "projectname/path.py" in them.

      The problem is, there is no way that I see with jenkins plugin to get it to actually run from that top level directory - it insists on using the first checkout path as the project base.

      I've tried all sorts of variants of overriding project base dir in the properties/etc. but it doesn't seem to work.

      Is there any way to force/override what jenkins passes to sonar runner as the project base dir?

            sonarteam Sonar Team
            nneul Nathan Neulinger
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: