-
Bug
-
Resolution: Unresolved
-
Major
-
O/S: Windows 7. Jenkins is installed as a windows service.
We have 1.499 version of Jenkins installed along with 1.44 Subversion plugin.
Though the correct credentials of Subversion repo were entered and accepted (Username/password authentication), while running the job it fails with the "E200015: No credential to try. Authentication failed" message. We have not been able to find a solution for this. We are getting this error message for all versions of Jenkins after 1.34
Please help in fixing this issue.
- is related to
-
JENKINS-15778 SVN Options Failure after upgrading Jenkins
-
- Open
-
-
JENKINS-17662 Sometime Jenkins could not checkout code from SVN
-
- Open
-
I hit this issue on a new installation. What's happening is the subversion access to the repository from the jenkins account is not initialized.
What you need to do is:
log into your account
sudo -i
su jenkins
cd /tmp
svn checkout https://part/of/your/repository
Subversion will prompt you for required credentials.
Once you have successfully checked out part of your repository, choosing to save credentials, you can exit the jenkins account and the sudo, then go back to your browser and your job configuration.
HTH