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

ERROR: Subversion update has been canceled

    XMLWordPrintable

Details

    • Bug
    • Status: Resolved (View Workflow)
    • Major
    • Resolution: Duplicate
    • subversion-plugin
    • None
    • Jenkins 1.610
      Subversion plugin 2.5
      Oracle JDK 1.7.0_67 x64
      Windows Server 2008 R2 Standard

    Description

      Subvresion update cancelled after job started.

      14:09:40 [EnvInject] - Loading node environment variables.
      14:09:40 Building on master in workspace C:\dev\jenkins\jobs\my-job\workspace
      14:09:40 Cleaning up C:\dev\jenkins\jobs\my-job\workspace\my-module
      14:09:45 Deleting C:\dev\jenkins\jobs\my-job\workspace\my-module\target
      14:09:45 Updating http://my-svn/trunk/my-module at revision '2015-04-21T14:09:40.817 +0300'
      14:09:50 ERROR: Subversion update has been canceled
      14:09:50 Build was aborted
      14:09:50 Finished: ABORTED

      Attachments

        Issue Links

          duplicates

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-29211 E200015: ISVNAuthentication provider did not provide credentials

          • Major - Major loss of function.
          • Resolved

          Activity

            Ascending order - Click to sort in descending order
            voji Pal Vojacsek added a comment -

            I experienced the same issue after upgrading svn plugin. When i checked the job page, the SCM part of configuration page indicate an error, because currently can't use any Credentials. When i re-set the proper credential fields, everything works again. I think the only issue is the error message, because it's misleading.

            voji Pal Vojacsek added a comment - I experienced the same issue after upgrading svn plugin. When i checked the job page, the SCM part of configuration page indicate an error, because currently can't use any Credentials. When i re-set the proper credential fields, everything works again. I think the only issue is the error message, because it's misleading.
            romaerzhuk Roman Erzhukov added a comment -

            Sorry. The reason of issue was empty credentials. It was strange error message. I did not understand right away.

            romaerzhuk Roman Erzhukov added a comment - Sorry. The reason of issue was empty credentials. It was strange error message. I did not understand right away.
            ricardogarfe Ricardo García Fernández added a comment -

            Hi,
            I have the same issue after updating the plugin (v2.5).

            Furthermore I need svn credentials in server to access svn 'via' sonarqube scm analysis.
            any ideas to fix this error or a workaround ?

            ricardogarfe Ricardo García Fernández added a comment - Hi, I have the same issue after updating the plugin (v2.5). Furthermore I need svn credentials in server to access svn 'via' sonarqube scm analysis. any ideas to fix this error or a workaround ?
            recena Manuel Recena Soto added a comment -

            Hi everyone. This bug is reached when you update to Subversion Plugin 2.5 from an old version (for example, 1.54). This update comes with an issue in the credentials migration process, that leads in a credentials lost.

            You can find more detailed information in JENKINS-29211 and its PR.

            recena Manuel Recena Soto added a comment - Hi everyone. This bug is reached when you update to Subversion Plugin 2.5 from an old version (for example, 1.54). This update comes with an issue in the credentials migration process, that leads in a credentials lost. You can find more detailed information in JENKINS-29211 and its PR .

            People

              recena Manuel Recena Soto
              romaerzhuk Roman Erzhukov
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: