Status: Open (View Workflow)
Environment:Linux 3.0.13-0.27-default #1 SMP Wed Feb 15 13:33:49 UTC 2012 (d73692b) x86_64 x86_64 x86_64 GNU/Linux
SUSE Linux Enterprise Server 11 (x86_64)
VERSION = 11
PATCHLEVEL = 2
When deploying Jenkins along Sonar 3.7.2 in the same Tomcat server and using the following startup configuration (Which is required for Sonar to work on Tomcat):
The installation is a single master instance, with no slaves.
We're getting an strange behaviour regarding the SVN credentials provision for each of the jobs, for some reason, we're getting a 403 Forbidden error even tough the credentials are fine and we're able to connect successfully to SVN via shell on the server.
So basically, if we start any of the jobs we have, it won't be able to obtain the corresponding credentials for Subversion and will fail, I have attached the error for your reference.
I've also tried deleting the subversion folder and even playing with several settings on the SVN server file.
Here's the thing, if I deploy Jenkins alone, it'll work just fine.
I'm suspecting this might be related to the fact that both Jenkins and Sonar are using JRuby, but since no further errors are being thrown I can't really tell much.
I tried replicating this error in Windows to no avail, so it might be an environment related thing as well.
Let me know if you need further information.