Getting authentication error using maven-release-plugin

Chris Flynn

We are attempting a release in Bamboo using Maven. The maven-release-plugin creates a tag in Subversion and uploads a artifact to the Nexus release repo. Both Nexus and Subversion can authenticate with the same user. We are storing that users credentials in our settings.xml.

When we run this release process from my laptop the process works fine.

When we run the process from Bamboo the process fails with an authentication error in Subversion. Nexus has no problems authenticating.

When we pass in the same user's credentials using the "-D" parameters the process works fine.

Does anyone know why there is a problem using the encrypted credentials from the settings.xml file?

We are using Bamboo v5.15

Chris Flynn

I believe the answer to this issue can be found at the below link. It is an issue with the Maven Release Plugin, not Bamboo.

http://maven.apache.org/maven-release/maven-release-plugin/faq.html#credentials

You add the the project.scm.id property to the POM file and set the property to a server id in Bamboo's setting.xml file. I used the same credentials that Maven uses for the Releases repository since that user exists in both my Nexus and Subversion repositories.

By setting this property the release plugin automatically knows to use the server credentials for committing code into Subversion. I plan on setting this property in a parent POM. That way the developers do not need to worry about including it and there is no extra setup when creating a release job in Bamboo.

<project>
   ...
    <properties>
      <project.scm.id>my-scm-server<project.scm.id>
    </properties>
  </project>

One note -- I discovered an issue on Windows if the password contains special characters. Subversion did not handle the special characters very gracefully and the job failed. Luckily our Bamboo instance runs on a Linux server and the special character does not cause any problems on Linux.