If you have SVN servers that only work with Kerberos authentication. For example VisualSVN installed on Windows operating system authenticating using Kerberos/Windows domain credentials/Active Directory.
The method described here requires Subversion configuration option "store-passwords = yes". It causes SVN to save the user credentials in a plain text file, which may not be suitable for everyone. Please check your security policies before continuing.
These instructions are loosely based on this forum entry by K. R. Walker on nabble.com. Originally I followed those instructions just to find out a bit later that the ticket cache (ticketCache option in jaas.conf) is never used by Hudson/svnkit. Instead it defaults to credentials stored by Subversion command line client. Please update this page when the proper Kerberos ticket based authentication starts to work.
1. Try out with an SVN client that your user can access your SVN repository. Store user credentials.
On Debian you could run:
The command will save your credentials in a file $HOME/.subversion/auth/svn.simple/. The file contains the user's password in plain text.
This verifies that the Kerberos authentication works. You should also check out something to verify that the user has read access.
You should add the options to the startup command of your Hudson java process:
On Debian you can add the variable JAVA_ARGS to the hudson settings in /etc/default/hudson :
To take the java properties and the new configuration in use.
In your Hudson-job configuration just add the SVN URL in Repository URL box. That can be found under Source Code Management -> Subversion.
NOTE: When you move the text pointer out of the text field, you will immediately see red error message, in case your configuration does not work. So if you see no error messages like in the above picture, you have succeeded. Congratulations!
Skip to end of metadata Go to start of metadata