[
https://issues.jenkins-ci.org/browse/JENKINS-12397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159289#comment-159289
]
SCM/JIRA link daemon commented on JENKINS-12397:
------------------------------------------------
Code changed in jenkins
User: Jakub Štiller
Path:
maven-plugin/src/main/java/hudson/maven/RedeployPublisher.java
maven-plugin/src/main/resources/hudson/maven/RedeployPublisher/config.jelly
maven-plugin/src/main/resources/hudson/maven/RedeployPublisher/help-releaseEnvVar.html
http://jenkins-ci.org/commit/jenkins/51a53ab491bc4efe1309655f0ba7df2050246409
Log:
JENKINS-12397: Skip deploying of artifacts when release build is running.
Monitor environment variable defined by user. If the variable is set to "true"
the deployment is skipped. The M2 Release plugin expose this kind of variables.
> Avoid post-build depoy to Maven repository in release build
> -----------------------------------------------------------
>
> Key: JENKINS-12397
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12397
> Project: Jenkins
> Issue Type: Bug
> Components: m2release
> Reporter: Kai Dyrssen
> Assignee: teilo
>
> The Jenkins post-build feature "deploy to Maven repository" in conjunction
> with a release build with m2release plugin leads to corrupt snapshot version
> in Maven snapshot repository:
> After the release build succeeds the post-build deploy deploys the new
> development version pom-file as old development version to our maven snapshot
> repository.
> If possible the m2release plugin should disable the post-build deploy feature
> in its release 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
