[JIRA] [m2release] (JENKINS-4560) POMs left in a modified state after failed release

Wed, 18 Dec 2013 07:10:36 -0800

This is a fairly nasty issue! Imagine this scenario:

  • A Maven build job "mvn clan deploy" or similar, which will deploy a new snapshot version on every build. Not too uncommon I think.
  • If a release build fails, the next build triggered on a code change will actually deploy to the repo based on the failed release version number (as the modified pom is left in the workspace)! And it could some time until people notice this and understand what has happened.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to