|
||||||||
|
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/d/optout.
The use case is that you want to split your job into two steps, where the first step does a "mvn clean verify" and the second step is then a "mvn deploy". By this one makes sure that you only deploy to your remote repository when the complete build was successful and don't deploy after each maven module which lead to incomplete deployments and all sort of problems, e.g. incompatible APIs, incompatible implementations, etc.
The other problem is that if there are two jobs as potential upstream candidates the job name tie breaker implementation kicks-in which chooses the upstream build based on the sorting of the job name. Although this is a deterministic behaviour IMO it would be better if also "verify" would be considered and takes precedence over the naming tie breaker. The change is completely backwards compatible but would allow support for jobs configuration which separate building and deploying into 2 steps as described above.
Hope this clarifies the reasoning behind the change. I think it is useful as a general feature to allow to split a job in two steps to make sure that only working builds are deployed.
As some time has passed I actually created a new pull request to update to more recent Jenkins version and also include a small bugfix, see https://github.com/jenkinsci/maven-plugin/pull/19.
I have the change running on a larger scale setup (> 2000 jobs) and am quite happy with it and also the feedback by developer teams that they only get "complete and consistent" artefact in the remote repository is positive.
Would be cool it this makes it into the maven plugin. Let me know if there is anything to improve in the pull request.