Maven release:prepare fails to commit tag

git maven-release-plugin
Peter N. Steinmetz picture Peter N. Steinmetz · Jun 4, 2012 · Viewed 13k times · Source

Attempting to perform a release on a maven project, which has successfully released before.

When I perform mvn release:prepare I am prompted for the release tags and the new snapshot tags and the project builds.

But when it attempts to push to the remote, I get

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.0:prepare (default-cli) on project NeuralAnalysis: Unable to tag SCM [ERROR] Provider message: [ERROR] The git-push command failed. [ERROR] Command output: [ERROR] To ssh://[email protected]/NeuralAnalysis.git [ERROR] ! [rejected] NeuralAnalysis-1.5.6 -> NeuralAnalysis-1.5.6 (non-fast-forward) [ERROR] error: failed to push some refs to 'ssh://[email protected]/NeuralAnalysis.git' [ERROR] To prevent you from losing history, non-fast-forward updates were rejected

And indeed, attempting to perform git push ssh://[email protected]/NeuralAnalysis.git NeuralAnalysis-1.5.6 manually, also exits with the same complaint.

Performing git pull says 'Already up-to-date'. git branch shows I am on the 'master'. git push origin gives 'Everything up-to-date'.

Looking at the repository using Tower shows that 'master', 'origin/master' and 'NeuralAnalysis-1.5.6' are all the same and on the last commit. The working directory contains release.properties and pom.xml.releaseBackup files.

It looks to me like everything is fine with the repository overall.

Answer

Peter N. Steinmetz picture Peter N. Steinmetz · Jun 4, 2012

Turns out it was a remote tag with the same name, as suggested by VonC in the comment. This was likely created by some previously aborted release.

Although I found the remote tag by manually inspecting the refs/tags directory on the remote repository, git ls-remote --tags will show them as well and the git push --verbose will also show more about the problem in general.

To fix this, first retrieve the remote tags with git fetch --tags.

One way to perform the next step is then to simply bypass that release tag by updating the pom.xml to have a higher -SNAPSHOT version (including any references in the same project by other modules to that snapshot), check these in, and do mvn release:clean; mvn release:prepare over again.

Related questions

"Git fatal: ref HEAD is not a symbolic ref" while using maven release plugin

I get the following error output while running the Maven release plugin prepare step i.e. mvn release:prepare --batch-mode -DreleaseVersion=1.1.2 -DdevelopmentVersion=1.2.0-SNAPSHOT -Dtag=v1.1.2 -X from an Atlassian Bamboo plan. However doing the same in the command line works …

Read More
Maven release plugin git credentials

We are using Jenkins and just switched from a file based git repo without authentication to using GitBlit with proper authentication over http. The problem is - how is maven supposed to authenticate itself in batch mode? Updating each job …

Read More
Maven Release Plugin use in Jenkins Pipeline

I'm using Jenkins Pipeline to automatically build and deploy my Java apps. I also use maven-release-plugin to perform Maven deploy to Artifactory. The problem is my Jenkinsfile (or Jenkins Pipeline Configuration) : We commit a version 0.1.00-SNAPSHOT on release branch Jenkins …

Read More