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

Double forwardslash in SVN URL causes Jenkins to repeatedly build

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • subversion-plugin
    • None

      After enabling the Poll SCM checkbox and setting the Schedule to "*/5 * * * *" in a SVN build job, Jenkins repeatedly builds the application every 5 minutes even when no source code changes have been made. This happens because there is a double forwardslash (e.g. //) somewhere in the Subversion Repository URL.

      Example:

      https://company.com/svnrepos//repo/src

      The source code is retrieved even though the URL is invalid and the job builds in an endless loop.

      WORKAROUND:

      Remove the double forwardslash from the Subversion Repository URL.

      Example:

      https://company.com/svnrepos/repo/src

          [JENKINS-14282] Double forwardslash in SVN URL causes Jenkins to repeatedly build

          kutzi added a comment -

          *reassigning to 'subversion' component

          kutzi added a comment - *reassigning to 'subversion' component

          evernat added a comment -

          I do not reproduce this issue: using the SVN URL http://javamelody.googlecode.com/svn//trunk/javamelody-core,
          I get only a second build with the following log:

          Lancé par un changement dans la base de code
Building in workspace C:\Applis\Jenkins\jobs\test\workspace
Switching from http://javamelody.googlecode.com/svn/trunk/javamelody-core to http://javamelody.googlecode.com/svn//trunk/javamelody-core
Switching to http://javamelody.googlecode.com/svn//trunk/javamelody-core at revision '2013-12-19T12:38:05.296 +0100'
At revision 3599
no revision recorded for http://javamelody.googlecode.com/svn//trunk/javamelody-core in the previous build

          So there is only a second build with a switch and no repeated builds.

          evernat added a comment - I do not reproduce this issue: using the SVN URL http://javamelody.googlecode.com/svn//trunk/javamelody-core , I get only a second build with the following log: Lancé par un changement dans la base de code Building in workspace C:\Applis\Jenkins\jobs\test\workspace Switching from http: //javamelody.googlecode.com/svn/trunk/javamelody-core to http://javamelody.googlecode.com/svn//trunk/javamelody-core Switching to http: //javamelody.googlecode.com/svn//trunk/javamelody-core at revision '2013-12-19T12:38:05.296 +0100' At revision 3599 no revision recorded for http: //javamelody.googlecode.com/svn//trunk/javamelody-core in the previous build So there is only a second build with a switch and no repeated builds.

          evernat added a comment -

          I think that this issue was fixed with JENKINS-2556 and https://github.com/jenkinsci/subversion-plugin/commit/6f3538ce695914395c3080741e117da0ff444ef3
          in the subversion plugin v1.48.
          So resolving as fixed.

          evernat added a comment - I think that this issue was fixed with JENKINS-2556 and https://github.com/jenkinsci/subversion-plugin/commit/6f3538ce695914395c3080741e117da0ff444ef3 in the subversion plugin v1.48. So resolving as fixed.

            Unassigned Unassigned
            bgwallace Brad Wallace
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: