[
https://issues.jenkins-ci.org/browse/JENKINS-12053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
domi resolved JENKINS-12053.
----------------------------
Resolution: Won't Fix
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.
> Sonar plugin fails execution on m2release execution
> ---------------------------------------------------
>
> Key: JENKINS-12053
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12053
> Project: Jenkins
> Issue Type: Improvement
> Components: m2release
> Affects Versions: current
> Environment: Jenkins 1.442; Sonar plugin 1.6.1; m2Release plugin 0.8.1
> Reporter: Justin Smith
> Assignee: teilo
> Priority: Minor
> Labels: release, sonar
>
> 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
