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

Sonar plugin fails execution on m2release execution

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Won't Fix
    • Icon: Minor Minor
    • m2release-plugin
    • Jenkins 1.442; Sonar plugin 1.6.1; m2Release plugin 0.8.1

      Our builds are configured to execute sonar with the Sonar plugin. This occurs after the initial reactor's build cycle completes, so all of the artifacts from the build have been installed to the local repo. On executing a release, the release performs as desired, but sonar executes after it is finished (as part of the jenkins build, but a separate reactor) with the new versions in the poms after the release. It fails because it cannot find the dependencies, because they have not been build/installed yet.

      Current work-around is to disable sonar for the release, execute release, enable sonar, run another build.

          [JENKINS-12053] Sonar plugin fails execution on m2release execution

          James Nord added a comment -

          normally you would want separate jobs for the on "commit/release" and "sonar" (after all the sonar report is maximum once a day right?)

          James Nord added a comment - normally you would want separate jobs for the on "commit/release" and "sonar" (after all the sonar report is maximum once a day right?)

          Dominik Bartholdi added a comment -

          This is unlikely to be fixed in the m2release plugin...
          But since version 0.9.0, the m2release plugin allows to reuse the normal build parameters: https://issues.jenkins-ci.org/browse/JENKINS-10127 and together with the latest Sonar plugin you are able to skip the sonar execution when ever you like.
          e.g. this will allow you to define a SKIP_SONAR parameter to skip the sonar analyzes for the release build.

          Dominik Bartholdi added a comment - This is unlikely to be fixed in the m2release plugin... But since version 0.9.0, the m2release plugin allows to reuse the normal build parameters: https://issues.jenkins-ci.org/browse/JENKINS-10127 and together with the latest Sonar plugin you are able to skip the sonar execution when ever you like. e.g. this will allow you to define a SKIP_SONAR parameter to skip the sonar analyzes for the release build.

            Unassigned Unassigned
            magno32 Justin Smith
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: