[
https://issues.apache.org/jira/browse/MRELEASE-954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16570341#comment-16570341
]
Thomas Mortagne commented on MRELEASE-954:
------------------------------------------
Big +1 on this one especially ending up on the remote repository with non
SNAPSHOT version even if for a brief period of time. We just been hit by this
issue with Jenkins being faster than the release plugin so yes it can happen :)
> maven-release-plugin should push less often to git server
> ---------------------------------------------------------
>
> Key: MRELEASE-954
> URL: https://issues.apache.org/jira/browse/MRELEASE-954
> Project: Maven Release Plugin
> Issue Type: Improvement
> Components: Git
> Affects Versions: 2.5.3
> Reporter: Markus Karg
> Priority: Minor
>
> mvn release:prepare runs three times git push which is bad:
> A single push at the end is enough to bring all commits and tags to the
> server finally
> It consumes more time than essentially necessary
> It is risky, because in case the first POM change A-SNAPSHOT -> A is pushed
> to the server but an error happens (bug in plugin, crash of client, whatever)
> then a "half prepared" state is on the server (the second POM change A ->
> B-SNAPSHOT is missing) and you cannot auto-recover from that without manual
> action (as mvn release:clean does not undo the tag). If there is only one
> single push at the end, then EVERYTHING, two commits and a tag, is pushed as
> a single transaction to the server, which is much better!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
