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

SCM polling always return true when using specific revision in svn

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • subversion-plugin
    • None
    • Hudson 1.379

      I have a build using 2 subversions module
      the first one contains the code base (on a branch), and is set to check out to HEAD
      the second one contains the build scripts and is set to use a specific revision using the @NNN feature in the svn url.
      It works great so far.

      this build is also setup to use SCM polling (obviously for the first module).
      the problem is, since i'm using a specific revision for the second module, the polling think there's always something new.

      in the scm polling log:
      svn://svnserver/deployment/scripts is at revision 185,800
      (changed from 184,375)

      and in the module i have as url : svn://svnserver/deployment/scripts@184375

      schedule for scm polling is */15 * * * *

      expected behavior : polling should not check for changes when using a specific revision, since it won't update anyway.

          [JENKINS-8554] SCM polling always return true when using specific revision in svn

          Ammon Riley added a comment -

          I disagree with the desired expected behaviour, because the premise "it won't update anyway" is wrong for the general case of @NNN. For example, if I use "@

          {00:00}

          ", I'd expect the polling to discover, and update changes every night, but ignore them during the day.

          I think a better option would be to have an option for each subversion module, as to whether or not it should be included in polling. That would also simplify triggering builds when only a specific portion of a large code-base changes, because the portions can be split into different modules.

          Ammon Riley added a comment - I disagree with the desired expected behaviour, because the premise "it won't update anyway" is wrong for the general case of @NNN. For example, if I use "@ {00:00} ", I'd expect the polling to discover, and update changes every night, but ignore them during the day. I think a better option would be to have an option for each subversion module, as to whether or not it should be included in polling. That would also simplify triggering builds when only a specific portion of a large code-base changes, because the portions can be split into different modules.

          I am experiencing this problem relating to the use of @NNN feature. Namely, when using it to pin a repository to a specific revision, if polling is enabled it will continuously trigger new builds. Is there any plan to look into this?

          Jose Pedro Correia added a comment - I am experiencing this problem relating to the use of @NNN feature. Namely, when using it to pin a repository to a specific revision, if polling is enabled it will continuously trigger new builds. Is there any plan to look into this?

            Unassigned Unassigned
            cactusbone cactusbone
            Votes:
            4 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated: