Our subversion server is access via an HTTPS proxy with a self signed certificate, and requires username/password authentication. I used keytool to add the certificate to the host operating systems installation of Sun Java 6. I also used Hudson to cache the subversion credentials. Everything was working fine until I created a job that uses the maven release plugin to release a module and deploy the artifacts.

I have the Hudson m2release plugin installed, but it has other problems and isn't working. This problem presented itself during a normal build with "-Dresume=false release:prepare release:perform". However I have no idea if this is a problem with Hudson, the Hudson Maven release plugin, the Maven release plugin, or the Maven scm plug-in.

The first problem I ran into was that the "svn" command was not found. However, as I mentioned, I already configured subversion within Hudson. Apparently the solution was to install subversion on the host. I did this, however, after this point the build was failing because of an SSL certificate problem, and then again because of an authentication problem.

I am somewhat new to Hudson, but it seems problematic for me to maintain two parallel instances of a subversion client on the CI machine. Hudson's for regular builds and a host instance for release builds.

Perhaps I am missing a setting or configuration somewhere?