|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
I have the same issue. I found a way of working around this problem:
Use the command line SVN settings in ~/.subversion/servers as described in http://svnbook.red-bean.com/en/1.6/svn-book.html#svn.serverconfig.httpd.ssl.client
Test this with the Subversion command line, e.g. svn info .
Jenkins now checks the repository URL ("https://...") when you type it into the job configuration, and finds that the connection is working, so it does not prompt you for credentials.
Works for me on Ubuntu 10.04.