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

"svn: E200015: No credential to try" - persistent

    Details

    • Similar Issues:

      Description

      After updating Jenkins from 1.551 to 1.565.2, our jobs fail, more often than not, with the SVN exception
      "E200015: No credential to try. Authentication failed"

      I know this has occurred before, but in our case, it keeps occurring, and there are no parameters involved. It doesn't happen every time, but about every second time.

      According to the SVN server's connection logs, Jenkins actually tries to connect to the SVN server without giving any credentials in those cases.

        Attachments

          Activity

          hjen Jennifer Hofmeister created issue -
          hjen Jennifer Hofmeister made changes -
          Field Original Value New Value
          Description After updating Jenkins from 1.551 to 1.565.2, our jobs fail, more often than not, with the SVN exception
          "E200015: No credential to try. Authentication failed"

          I know this has occurred before, but in our case, it is neither externals-only nor are there any parameters involved. Also, it is not restricted the first one. It doesn't happen every time, but about every second time.

          According to the SVN server's connection logs, Jenkins actually tries to connect to the SVN server without giving any credentials in those cases.
          After updating Jenkins from 1.551 to 1.565.2, our jobs fail, more often than not, with the SVN exception
          "E200015: No credential to try. Authentication failed"

          I know this has occurred before, but in our case, it is neither externals-only nor are there any parameters involved. Also, it is not restricted the first one. It doesn't happen every time, but about every second time.

          According to the SVN server's connection logs, Jenkins actually tries to connect to the SVN server without giving any credentials in those cases.

          Might be related to https://issues.jenkins-ci.org/browse/JENKINS-25147 becauset the two started occurring at the same time.
          Hide
          danielbeck Daniel Beck added a comment -

          Report needs logging output. Create a log recorder in /log, add a bunch of SVN related loggers and set them to 'ALL'.

          Show
          danielbeck Daniel Beck added a comment - Report needs logging output. Create a log recorder in /log, add a bunch of SVN related loggers and set them to 'ALL'.
          hjen Jennifer Hofmeister made changes -
          Description After updating Jenkins from 1.551 to 1.565.2, our jobs fail, more often than not, with the SVN exception
          "E200015: No credential to try. Authentication failed"

          I know this has occurred before, but in our case, it is neither externals-only nor are there any parameters involved. Also, it is not restricted the first one. It doesn't happen every time, but about every second time.

          According to the SVN server's connection logs, Jenkins actually tries to connect to the SVN server without giving any credentials in those cases.

          Might be related to https://issues.jenkins-ci.org/browse/JENKINS-25147 becauset the two started occurring at the same time.
          After updating Jenkins from 1.551 to 1.565.2, our jobs fail, more often than not, with the SVN exception
          "E200015: No credential to try. Authentication failed"

          I know this has occurred before, but in our case, it keeps occurring, and there are no parameters involved. Also, it is not restricted the first one. It doesn't happen every time, but about every second time.

          According to the SVN server's connection logs, Jenkins actually tries to connect to the SVN server without giving any credentials in those cases.

          Might be related to https://issues.jenkins-ci.org/browse/JENKINS-25147 becauset the two started occurring at the same time.
          Hide
          hjen Jennifer Hofmeister added a comment -

          On it. Just made a quick edit: it does seem to be externals-only.

          Show
          hjen Jennifer Hofmeister added a comment - On it. Just made a quick edit: it does seem to be externals-only.
          hjen Jennifer Hofmeister made changes -
          Description After updating Jenkins from 1.551 to 1.565.2, our jobs fail, more often than not, with the SVN exception
          "E200015: No credential to try. Authentication failed"

          I know this has occurred before, but in our case, it keeps occurring, and there are no parameters involved. Also, it is not restricted the first one. It doesn't happen every time, but about every second time.

          According to the SVN server's connection logs, Jenkins actually tries to connect to the SVN server without giving any credentials in those cases.

          Might be related to https://issues.jenkins-ci.org/browse/JENKINS-25147 becauset the two started occurring at the same time.
          After updating Jenkins from 1.551 to 1.565.2, our jobs fail, more often than not, with the SVN exception
          "E200015: No credential to try. Authentication failed"

          I know this has occurred before, but in our case, it keeps occurring, and there are no parameters involved. It doesn't happen every time, but about every second time.

          According to the SVN server's connection logs, Jenkins actually tries to connect to the SVN server without giving any credentials in those cases.

          Might be related to https://issues.jenkins-ci.org/browse/JENKINS-25147 becauset the two started occurring at the same time.
          hjen Jennifer Hofmeister made changes -
          Description After updating Jenkins from 1.551 to 1.565.2, our jobs fail, more often than not, with the SVN exception
          "E200015: No credential to try. Authentication failed"

          I know this has occurred before, but in our case, it keeps occurring, and there are no parameters involved. It doesn't happen every time, but about every second time.

          According to the SVN server's connection logs, Jenkins actually tries to connect to the SVN server without giving any credentials in those cases.

          Might be related to https://issues.jenkins-ci.org/browse/JENKINS-25147 becauset the two started occurring at the same time.
          After updating Jenkins from 1.551 to 1.565.2, our jobs fail, more often than not, with the SVN exception
          "E200015: No credential to try. Authentication failed"

          I know this has occurred before, but in our case, it keeps occurring, and there are no parameters involved. It doesn't happen every time, but about every second time.

          According to the SVN server's connection logs, Jenkins actually tries to connect to the SVN server without giving any credentials in those cases.
          Hide
          danielbeck Daniel Beck added a comment -

          Duplicates JENKINS-21785 then.

          Show
          danielbeck Daniel Beck added a comment - Duplicates JENKINS-21785 then.
          danielbeck Daniel Beck made changes -
          Status Open [ 1 ] Resolved [ 5 ]
          Resolution Duplicate [ 3 ]
          stephenconnolly Stephen Connolly made changes -
          Status Resolved [ 5 ] Closed [ 6 ]
          rtyler R. Tyler Croy made changes -
          Workflow JNJira [ 159057 ] JNJira + In-Review [ 208129 ]

            People

            • Assignee:
              stephenconnolly Stephen Connolly
              Reporter:
              hjen Jennifer Hofmeister
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: