Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-16343

Access to the Subversion repository doesn't work via the subversion plugin - Always get a E200015: No credential to try. Authentication failed error.

      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.

          [JENKINS-16343] Access to the Subversion repository doesn't work via the subversion plugin - Always get a E200015: No credential to try. Authentication failed error.

          Roy Wright added a comment -

          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

          Roy Wright added a comment - 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

          ily naf added a comment - - edited

          Happens here with Jenkins 1.514, Subversion plugin 1.45, Subversion server 1.6.5 (https + SSLv3). Doesn't happen with SVN server 1.5.5 (https + TLSv1) on the same Jenkins + Subversion plugin. This is quite annoying & the workaround requires manipulation on all nodes (master, slaves). Please consider a fix for this roadblock ASAP. Tks!

          ily naf added a comment - - edited Happens here with Jenkins 1.514, Subversion plugin 1.45, Subversion server 1.6.5 (https + SSLv3). Doesn't happen with SVN server 1.5.5 (https + TLSv1) on the same Jenkins + Subversion plugin. This is quite annoying & the workaround requires manipulation on all nodes (master, slaves). Please consider a fix for this roadblock ASAP. Tks!

          kutzi added a comment -

          Sounds similar to JENKINS-15778

          kutzi added a comment - Sounds similar to JENKINS-15778

          ily naf added a comment -

          They could be related because we also apply the workaround "-Dsvnkit.http.sslProtocols=SSLv3" here.

          ily naf added a comment - They could be related because we also apply the workaround "-Dsvnkit.http.sslProtocols=SSLv3" here.

          Angel Williams added a comment - - edited

          I am currently using: Jenkins 1.546 with Subversion Plugin: 2.2 and Credentials Plugin: 1.1

          I was able to fix the builds so they at least downloaded by opending tortoiseSVN on each Node and saving the password for the Repository.
          At least now I have builds.
          Which means I have to store credentials on systems for this to work and that is not good especially since it is my credentials.

          I tried going to current Jenkins 1.554 recently but all my Windows Slaves no longer connected so I need to make sure any upgrades are going to work because I do not want to store credentials on all the slave machines.

          Angel Williams added a comment - - edited I am currently using: Jenkins 1.546 with Subversion Plugin: 2.2 and Credentials Plugin: 1.1 I was able to fix the builds so they at least downloaded by opending tortoiseSVN on each Node and saving the password for the Repository. At least now I have builds. Which means I have to store credentials on systems for this to work and that is not good especially since it is my credentials. I tried going to current Jenkins 1.554 recently but all my Windows Slaves no longer connected so I need to make sure any upgrades are going to work because I do not want to store credentials on all the slave machines.

            Unassigned Unassigned
            kningthouj K Ningthouj
            Votes:
            3 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated: