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

Subversion Polling does not work properly whenever using variables in the Repository URL

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Blocker Blocker
    • subversion-plugin
    • None
    • Jenkins ver. 1.549
      Running on Windows server
      Java 7

      After the last subversion plugin update, we start to face some endless job executions. Even when no new commits were performed in the SVN repository.

      We have found in the subversion pooling log that it was unable to check for changes in the SVN repository so, because of this, it decided to rebuild the job.

      The workaround was to use static URL in the repository url input.

          [JENKINS-21625] Subversion Polling does not work properly whenever using variables in the Repository URL

          This might be related to not using the correct credentials.

          Marcel Beister added a comment - This might be related to not using the correct credentials.

          Hi Marcel,

          I've fixed the issue related to the credential and then I got this error.

          As you can see in the stack trace bellow, Subversion Plugin is not using the variables/parameters anymore while it is polling the repository. So, it assumes that there are changes.

          tarted on Feb 3, 2014 2:39:34 PM
          ERROR: Failed to check repository revision for ${PROJECT_SVN_REPO}/trunk/${PROJECT_NAME}
          org.tmatesoft.svn.core.SVNException: svn: E125002: Malformed URL '${PROJECT_SVN_REPO}/trunk/${PROJECT_NAME}'
          at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:64)
          at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51)
          at org.tmatesoft.svn.core.SVNURL.<init>(SVNURL.java:233)
          at org.tmatesoft.svn.core.SVNURL.parseURIEncoded(SVNURL.java:127)
          at hudson.scm.SubversionSCM$ModuleLocation.getSVNURL(SubversionSCM.java:2785)
          at hudson.scm.SubversionSCM.compareRemoteRevisionWith(SubversionSCM.java:1436)
          at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:356)
          at hudson.scm.SCM.poll(SCM.java:373)
          at hudson.model.AbstractProject._poll(AbstractProject.java:1581)
          at hudson.model.AbstractProject.poll(AbstractProject.java:1490)
          at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:462)
          at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:491)
          at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118)
          at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
          at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
          at java.util.concurrent.FutureTask.run(Unknown Source)
          at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
          at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
          at java.lang.Thread.run(Unknown Source)
          Caused by: svn: E125002: Malformed URL '${PROJECT_SVN_REPO}/trunk/${PROJECT_NAME}'
          at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:171)
          at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:126)
          at org.tmatesoft.svn.core.SVNURL.<init>(SVNURL.java:232)
          ... 16 more
          Done. Took 0.49 sec
          Changes found

          Fernando Rubbo added a comment - Hi Marcel, I've fixed the issue related to the credential and then I got this error. As you can see in the stack trace bellow, Subversion Plugin is not using the variables/parameters anymore while it is polling the repository. So, it assumes that there are changes. tarted on Feb 3, 2014 2:39:34 PM ERROR: Failed to check repository revision for ${PROJECT_SVN_REPO}/trunk/${PROJECT_NAME} org.tmatesoft.svn.core.SVNException: svn: E125002: Malformed URL '${PROJECT_SVN_REPO}/trunk/${PROJECT_NAME}' at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:64) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51) at org.tmatesoft.svn.core.SVNURL.<init>(SVNURL.java:233) at org.tmatesoft.svn.core.SVNURL.parseURIEncoded(SVNURL.java:127) at hudson.scm.SubversionSCM$ModuleLocation.getSVNURL(SubversionSCM.java:2785) at hudson.scm.SubversionSCM.compareRemoteRevisionWith(SubversionSCM.java:1436) at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:356) at hudson.scm.SCM.poll(SCM.java:373) at hudson.model.AbstractProject._poll(AbstractProject.java:1581) at hudson.model.AbstractProject.poll(AbstractProject.java:1490) at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:462) at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:491) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: svn: E125002: Malformed URL '${PROJECT_SVN_REPO}/trunk/${PROJECT_NAME}' at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:171) at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:126) at org.tmatesoft.svn.core.SVNURL.<init>(SVNURL.java:232) ... 16 more Done. Took 0.49 sec Changes found

          I had the credential issue as well when upgrading... Which I fixed!

          And now I get the exact same issue as Fernando Rubbo. Since the plugin fails to get the revision, it assumes there were changes and schedules a build every 5 minutes.

          The builds are successfuls (the checkout works fine). Only the 'check for changes' doesn't work with variables!

          Jérémie Faucher-Goulet added a comment - I had the credential issue as well when upgrading... Which I fixed! And now I get the exact same issue as Fernando Rubbo. Since the plugin fails to get the revision, it assumes there were changes and schedules a build every 5 minutes. The builds are successfuls (the checkout works fine). Only the 'check for changes' doesn't work with variables!

          Milos Svasek added a comment -

          Please fix it, it's blocker for us!
          We really need to use variables in Subversion URL.

          Thanks in advance.

          Milos Svasek added a comment - Please fix it, it's blocker for us! We really need to use variables in Subversion URL. Thanks in advance.

          Daniel Beck added a comment -

          Specify matching 'Additional Credentials' as described in comments to JENKINS-21785 – it should work for this issue as well.

          Daniel Beck added a comment - Specify matching 'Additional Credentials' as described in comments to JENKINS-21785 – it should work for this issue as well.

          Daniel Beck added a comment -

          Seems to duplicate JENKINS-23007. I've already submitted a patch for that one, so resolving this one.

          Daniel Beck added a comment - Seems to duplicate JENKINS-23007 . I've already submitted a patch for that one, so resolving this one.

          Tim Bradt added a comment -

          This is still a problem in Subversion plug-in 2.5...

          Started on Apr 10, 2015 3:42:02 PM
          ERROR: Failed to check repository revision for ${SVN_URL_ROOT}30-Dev/DatabaseBuild
          org.tmatesoft.svn.core.SVNException: svn: E125002: Malformed URL '${SVN_URL_ROOT}30-Dev/DatabaseBuild'

          I don't have any credential issues.

          Tim Bradt added a comment - This is still a problem in Subversion plug-in 2.5... Started on Apr 10, 2015 3:42:02 PM ERROR: Failed to check repository revision for ${SVN_URL_ROOT}30-Dev/DatabaseBuild org.tmatesoft.svn.core.SVNException: svn: E125002: Malformed URL '${SVN_URL_ROOT}30-Dev/DatabaseBuild' I don't have any credential issues.

          Lionel Trebuchon added a comment - - edited

          Hello!

          I also use the svn plugin 2.5.
          For me, the passing of environment variables defined on folder level (or on jenkins level, whatever you use) works well when I am building on... linux (debian)!
          The ${PATH_TO_MY_SOFTWARE} expands like a charme into the true link.

          On Windows however, ${PATH_TO_MY_COMPILERS} and %PATH_TO_MY_SOFTWARE% that same mistake "ERROR: Failed to check out %SVN_PERIPHERALS-P2_LATEST%/fdoot_mpd
          org.tmatesoft.svn.core.SVNException: svn: E125002: Malformed URL "

          I don't know if this piece of information helps anyone. I am still waiting for the Windows solution, the Linux solution seems to work (I really didn't have to tweak anything)
          Friendly Greetings, and have a wonderful day!
          Lionel

          Lionel Trebuchon added a comment - - edited Hello! I also use the svn plugin 2.5. For me, the passing of environment variables defined on folder level (or on jenkins level, whatever you use) works well when I am building on... linux (debian) ! The ${PATH_TO_MY_SOFTWARE} expands like a charme into the true link. On Windows however, ${PATH_TO_MY_COMPILERS} and %PATH_TO_MY_SOFTWARE% that same mistake "ERROR: Failed to check out %SVN_PERIPHERALS-P2_LATEST%/fdoot_mpd org.tmatesoft.svn.core.SVNException: svn: E125002: Malformed URL " I don't know if this piece of information helps anyone. I am still waiting for the Windows solution, the Linux solution seems to work (I really didn't have to tweak anything) Friendly Greetings, and have a wonderful day! Lionel

          Pascal Heinrich added a comment - - edited

          I still have exact the same problem with subversion plugin version 2.7.1 I do not see this issue Resolved.

          Pascal Heinrich added a comment - - edited I still have exact the same problem with subversion plugin version 2.7.1 I do not see this issue Resolved.

            Unassigned Unassigned
            fbrubbo Fernando Rubbo
            Votes:
            9 Vote for this issue
            Watchers:
            15 Start watching this issue

              Created:
              Updated:
              Resolved: