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

Sonar plugin fails execution on m2release execution

    XMLWordPrintable

Details

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

    Description

      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.

      Attachments

        Activity

          People

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

            Dates

              Created:
              Updated:
              Resolved: