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

builds (SCM polling based) are triggered even when there are no (SVN) SCM changes

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • core
    • None
    • Win2003 R2 32bit, JDK 1.6.0_18, Tomcat 6.0.20, Hudson 1.350, Subversion plugin 1.13

      in the past few days I noticed a lot of job builds on our Hudson instance are triggered when there are no SCM changes.

      the subversion polling log reports:
      =============================================================
      Last Subversion Polling Log

      Started on 13-Mar-2010 11:46:43

      https://URL/to/repo is at revision 58,781

      Done. Took 1.2 sec

      No changes
      =============================================================

      the build log reports:
      =============================================================
      Revision: 58781
      No changes.

      Started by an SCM change
      =============================================================

      The catalina log is also clean:
      =============================================================
      13-Mar-2010 11:46:43 hudson.triggers.SCMTrigger$Runner run
      INFO: SCM changes detected in JobName. Triggering #491
      ...
      13-Mar-2010 11:47:35 hudson.model.Run run
      INFO: JobName #491 main build action completed: SUCCESS
      =============================================================

      It is really puzzling me...

          [JENKINS-5926] builds (SCM polling based) are triggered even when there are no (SVN) SCM changes

          Andrea Barbieri created issue -
          Andrea Barbieri made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: Open [ 1 ] New: Closed [ 6 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 136018 ] New: JNJira + In-Review [ 203803 ]

            Unassigned Unassigned
            abarbieri Andrea Barbieri
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: