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

List Subversion Tags job parameter wants svn credentials but there is no way to fill it

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Critical Critical
    • subversion-plugin
    • None
    • jenkins 1.549
      subversion plugin 2.0

      steps to reproduce:
      1. add "List Subversion Tags" parameter at dummy job
      2. input any valid svn+ssh url to "Repository URL" field

      there is a red message: Unable to access svn+ssh://my_svn_url.com : svn: E200015: No credential to try. Authentication failed (show details)
      but there is no any dropdowns to fill credentials

          [JENKINS-21617] List Subversion Tags job parameter wants svn credentials but there is no way to fill it

          Matthias Kolonko added a comment - - edited

          when clicking on this link provided by the parameter form (FailedWorkaround1) ...

          Matthias Kolonko added a comment - - edited when clicking on this link provided by the parameter form (FailedWorkaround1) ...

          Matthias Kolonko added a comment - - edited

          ... you get this (FailedWorkaround2).

          This issue causes immense problems as our whole CI environment for all our builds depend on it.
          So, for us it is not only critical - it is nearly a blocker!

          I tried another workaround by using a text field parameter where the particular branch or tag can be typed in instead of choosing from a list.
          But I failed getting the same error message!
          (Not very suprprising as this parameter type does not care about Subversion. )

          It seems like the provided parameter setting of the plugin does not conform to the new credentials framework where you can choose from a list of saved credentials.
          But: The main part of the plugin that can be found in the section "Source Code Management" does that now.
          Hence, it seems like an inconsistency.

          It would be highly appreciated if this bug would be fixed soon according to the mentioned situation.

          Matthias Kolonko added a comment - - edited ... you get this (FailedWorkaround2). This issue causes immense problems as our whole CI environment for all our builds depend on it. So, for us it is not only critical - it is nearly a blocker! I tried another workaround by using a text field parameter where the particular branch or tag can be typed in instead of choosing from a list. But I failed getting the same error message! (Not very suprprising as this parameter type does not care about Subversion. ) It seems like the provided parameter setting of the plugin does not conform to the new credentials framework where you can choose from a list of saved credentials. But: The main part of the plugin that can be found in the section "Source Code Management" does that now. Hence, it seems like an inconsistency. It would be highly appreciated if this bug would be fixed soon according to the mentioned situation.

          2.1

          Stephen Connolly added a comment - 2.1

          2.1 seems to fix this problem for us

          Marcel Beister added a comment - 2.1 seems to fix this problem for us

          Same here.
          All seems to work properly again!
          Just had to delete the workspace for one project and do a complete new checkout, but now it's OK.

          I guess this issue can be closed.

          Matthias Kolonko added a comment - Same here. All seems to work properly again! Just had to delete the workspace for one project and do a complete new checkout, but now it's OK. I guess this issue can be closed.

          My problems are fixed with Release2.1

          Alexander Fischer added a comment - My problems are fixed with Release2.1

          Kevin Brand added a comment -

          I've got the same problem, using the Subversion Tagging Plugin.
          I'm using Release2.1 as well, Subversion Tagging Plugin Version 1.16 on Jenkins 1.550.

          When trying to tag a successfull build I get this errormessage:
          "Das Erstellen des Tags ist fehlgeschlagen. svn: E200015: OPTIONS /svn/tools/Redmine/Changelog/trunk failed
          Build step 'Erstellt Subversion Tags für erfolgreiche Builds.' marked build as failure"
          Which means "The creating of the tag failed. svn: E200015: OPTIONS /svn/tools/Redmine/Changelog/trunk failed
          Build step 'Creates Subversion tag for successfull Builds.' marked build as failure"

          It seems to be the same problem, caused by the missing credentials.

          Kevin Brand added a comment - I've got the same problem, using the Subversion Tagging Plugin. I'm using Release2.1 as well, Subversion Tagging Plugin Version 1.16 on Jenkins 1.550. When trying to tag a successfull build I get this errormessage: "Das Erstellen des Tags ist fehlgeschlagen. svn: E200015: OPTIONS /svn/tools/Redmine/Changelog/trunk failed Build step 'Erstellt Subversion Tags für erfolgreiche Builds.' marked build as failure" Which means "The creating of the tag failed. svn: E200015: OPTIONS /svn/tools/Redmine/Changelog/trunk failed Build step 'Creates Subversion tag for successfull Builds.' marked build as failure" It seems to be the same problem, caused by the missing credentials.

          Hi Stephen,

          I'm using Jenkins 1.555, and tried svn plugin 2.1 and 2.2.

          Even with configured credentials (which are working for checkouts), i face an error :

          ERROR: Failed to tag
          org.tmatesoft.svn.core.SVNCancelException: svn: E200015: OPTIONS /svn/java/fr.infuz.matrixlock/trunk failed
          at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:384)
          at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:373)
          at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:361)
          at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:707)
          at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.exchangeCapabilities(DAVConnection.java:627)
          at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.open(DAVConnection.java:102)
          at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.openConnection(DAVRepository.java:1020)
          at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.getRepositoryRoot(DAVRepository.java:132)
          at org.tmatesoft.svn.core.internal.wc.SVNCopyDriver.copyReposToRepos(SVNCopyDriver.java:194)
          at org.tmatesoft.svn.core.internal.wc.SVNCopyDriver.setupCopy(SVNCopyDriver.java:627)
          at org.tmatesoft.svn.core.internal.wc16.SVNCopyClient16.doCopy(SVNCopyClient16.java:440)
          at org.tmatesoft.svn.core.internal.wc2.remote.SvnNgReposToReposCopy.run(SvnNgReposToReposCopy.java:65)
          at org.tmatesoft.svn.core.internal.wc2.remote.SvnNgReposToReposCopy.run(SvnNgReposToReposCopy.java:23)
          at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:20)
          at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1238)
          at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294)
          at org.tmatesoft.svn.core.wc2.SvnRemoteCopy.run(SvnRemoteCopy.java:227)
          at org.tmatesoft.svn.core.wc.SVNCopyClient.doCopy(SVNCopyClient.java:480)
          at hudson.scm.SubversionTagAction$TagWorkerThread.perform(SubversionTagAction.java:306)
          at hudson.model.TaskThread.run(TaskThread.java:127)
          Caused by: org.tmatesoft.svn.core.SVNCancelException: svn: E200015: No credential to try. Authentication failed
          at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.cancel(SVNErrorManager.java:37)
          at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.cancel(SVNErrorManager.java:32)
          at org.tmatesoft.svn.core.internal.wc.DefaultSVNAuthenticationManager.getNextAuthentication(DefaultSVNAuthenticationManager.java:223)
          at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection._request(HTTPConnection.java:697)
          at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:382)
          ... 19 more
          Completed

          As my credential is working for checkout, i wonder why its not working for tag.

          aurelien Labrosse added a comment - Hi Stephen, I'm using Jenkins 1.555, and tried svn plugin 2.1 and 2.2. Even with configured credentials (which are working for checkouts), i face an error : ERROR: Failed to tag org.tmatesoft.svn.core.SVNCancelException: svn: E200015: OPTIONS /svn/java/fr.infuz.matrixlock/trunk failed at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:384) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:373) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:361) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:707) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.exchangeCapabilities(DAVConnection.java:627) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.open(DAVConnection.java:102) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.openConnection(DAVRepository.java:1020) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.getRepositoryRoot(DAVRepository.java:132) at org.tmatesoft.svn.core.internal.wc.SVNCopyDriver.copyReposToRepos(SVNCopyDriver.java:194) at org.tmatesoft.svn.core.internal.wc.SVNCopyDriver.setupCopy(SVNCopyDriver.java:627) at org.tmatesoft.svn.core.internal.wc16.SVNCopyClient16.doCopy(SVNCopyClient16.java:440) at org.tmatesoft.svn.core.internal.wc2.remote.SvnNgReposToReposCopy.run(SvnNgReposToReposCopy.java:65) at org.tmatesoft.svn.core.internal.wc2.remote.SvnNgReposToReposCopy.run(SvnNgReposToReposCopy.java:23) at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:20) at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1238) at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294) at org.tmatesoft.svn.core.wc2.SvnRemoteCopy.run(SvnRemoteCopy.java:227) at org.tmatesoft.svn.core.wc.SVNCopyClient.doCopy(SVNCopyClient.java:480) at hudson.scm.SubversionTagAction$TagWorkerThread.perform(SubversionTagAction.java:306) at hudson.model.TaskThread.run(TaskThread.java:127) Caused by: org.tmatesoft.svn.core.SVNCancelException: svn: E200015: No credential to try. Authentication failed at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.cancel(SVNErrorManager.java:37) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.cancel(SVNErrorManager.java:32) at org.tmatesoft.svn.core.internal.wc.DefaultSVNAuthenticationManager.getNextAuthentication(DefaultSVNAuthenticationManager.java:223) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection._request(HTTPConnection.java:697) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:382) ... 19 more Completed As my credential is working for checkout, i wonder why its not working for tag.

          I am experiencing the same issue.
          Jenkins v1.551
          svn plugin 2.2
          Subversion copy failed. svn: E200015

          what is the resolution?

          linda mcdonald added a comment - I am experiencing the same issue. Jenkins v1.551 svn plugin 2.2 Subversion copy failed. svn: E200015 what is the resolution?

          mavlyutov Are you using currently svn:+ssh:// protocol?

          Manuel Recena Soto added a comment - mavlyutov Are you using currently svn:+ssh:// protocol?

            recena Manuel Recena Soto
            mavlyutov Marat Mavlyutov
            Votes:
            11 Vote for this issue
            Watchers:
            14 Start watching this issue

              Created:
              Updated: