• Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Critical Critical
    • subversion-plugin
    • None
    • Platform: All, OS: All

      I have a project which is triggered by subversion changes. It has 3 repository
      URLs specified. Update is de-selected.

      Since I upgraded to 1.286, checkouts are not being triggered. What appears to be
      the case is this:

      Previously, a change in any of the repositories would trigger a checkout. In
      1.286, it appears that a checkout is only triggered if a change in the LAST of
      the listed repositories is detected.

      This has been observed by another user as well (except that he used update). He
      reported that downgrading to 1.285 fixed the problem.

          [JENKINS-3168] SVN polling broken in 1.286

          Matthew Webber created issue -

          When you see the subversion polling log output from the project page, what do
          you see there?

          Kohsuke Kawaguchi added a comment - When you see the subversion polling log output from the project page, what do you see there?
          Kohsuke Kawaguchi made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]
          Kohsuke Kawaguchi made changes -
          Status Original: In Progress [ 3 ] New: Open [ 1 ]

          This issue appears to be a regression caused by rev.15650 for issue #3164.
          Reassigning.

          Kohsuke Kawaguchi added a comment - This issue appears to be a regression caused by rev.15650 for issue #3164. Reassigning.

          Information previded as requested: The subversion polling log output from the
          project page shows:

          Started on 27-Feb-2009 15:02:22
          https://trac.diamond.ac.uk/svn/gda/trunk/configurations/diamond is at revision
          13,669
          Done. Took 2.6 sec
          No changes

          There are 3 respository URLs specified in the following order:
          https://trac.diamond.ac.uk/svn/gda/trunk/gda
          https://trac.diamond.ac.uk/svn/gda/trunk/configurations/diamond
          https://trac.diamond.ac.uk/svn/gda/trunk/configurations/diamond

          Matthew Webber added a comment - Information previded as requested: The subversion polling log output from the project page shows: Started on 27-Feb-2009 15:02:22 https://trac.diamond.ac.uk/svn/gda/trunk/configurations/diamond is at revision 13,669 Done. Took 2.6 sec No changes There are 3 respository URLs specified in the following order: https://trac.diamond.ac.uk/svn/gda/trunk/gda https://trac.diamond.ac.uk/svn/gda/trunk/configurations/diamond https://trac.diamond.ac.uk/svn/gda/trunk/configurations/diamond

          Alan Harder added a comment -

          add cc

          Alan Harder added a comment - add cc

          Alan Harder added a comment -
              • Issue 3183 has been marked as a duplicate of this issue. ***

          Alan Harder added a comment - Issue 3183 has been marked as a duplicate of this issue. ***
          Alan Harder made changes -
          Link New: This issue is duplicated by JENKINS-3183 [ JENKINS-3183 ]

          cutterslade added a comment -

          I have also noticed this issue, although with slightly different circumstances.

          Several of my projects use the svn:externals property to link two projects, and
          several branches from each together. After upgrading from 1.285 to 1.287,
          builds are not being triggered by changes to the external branches. The SVN
          Polling log indicates that only the top level (the URL configured for the build)
          is being checked, before the upgrade, the polling log would include revision
          numbers of each of the external branches.

          cutterslade added a comment - I have also noticed this issue, although with slightly different circumstances. Several of my projects use the svn:externals property to link two projects, and several branches from each together. After upgrading from 1.285 to 1.287, builds are not being triggered by changes to the external branches. The SVN Polling log indicates that only the top level (the URL configured for the build) is being checked, before the upgrade, the polling log would include revision numbers of each of the external branches.

            mindless Alan Harder
            mwebber Matthew Webber
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: