• Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major Major
    • subversion-plugin
    • None
    • Platform: All, OS: All

      I have upgraded from 1.115 to 1.122 today. Build for our projects is triggered
      by changes in svn. We are using user name & password to access svn.

      After the upgrade quite often the build gets triggered even when there are no
      changes in the svn (it even says no changes on the build page). Also while a
      build is running another build for the same project gets added to teh queue and
      starts right away after the previous buidl is done (ignoring the quite period
      settings)

      (you are doign an amazing job with Hudson, i can't believe we were able to
      exist without it before we switched about 4 months ago!)

          [JENKINS-688] Build is executed with no changes (svn)

          I know this is the older issue, but since I've already posted my comment to
          #692, I'm merging this into #692 too.

              • This issue has been marked as a duplicate of 692 ***

          Kohsuke Kawaguchi added a comment - I know this is the older issue, but since I've already posted my comment to #692, I'm merging this into #692 too. This issue has been marked as a duplicate of 692 ***

          stanoislav added a comment -

          I'm not able to post comments into #692 so I'm enterign it here.

          In 128 I still see the issue.

          On checkin to svn a new build enters a que and this is in the svn pooling log:

          Started on Aug 12, 2007 7:55:18 AM
          Revision:103133
          (changed from 103128)
          Done. Took 0 seconds
          Changes found

          When the build starts (we have 3 minutes quiet period) immediately another
          build is added to the queue even that there were no other changes after those
          that have triggered the build that just started building. The log still shows
          the same:

          Started on Aug 12, 2007 7:56:18 AM
          Revision:103133
          (changed from 103128)
          Done. Took 0 seconds
          Changes found

          The full hudson log from that period is here:

          Aug 12, 2007 7:56:18 AM hudson.triggers.SCMTrigger$Runner run
          INFO: SCM changes detected in V2BP Continuous Build. Job is already in the queue

          Aug 12, 2007 7:56:18 AM hudson.triggers.SCMTrigger$Runner runPolling
          INFO: Polling SCM changes of V2BP Continuous Build

          Aug 12, 2007 7:55:18 AM hudson.triggers.SCMTrigger$Runner run
          INFO: SCM changes detected in V2BP Continuous Build. Triggering #2233

          Aug 12, 2007 7:55:18 AM hudson.triggers.SCMTrigger$Runner runPolling
          INFO: Polling SCM changes of V2BP Continuous Build

          Aug 12, 2007 7:54:18 AM hudson.triggers.SCMTrigger$Runner run
          INFO: SCM changes detected in V2BP Continuous Build. Triggering #2233

          Aug 12, 2007 7:54:18 AM hudson.triggers.SCMTrigger$Runner runPolling
          INFO: Polling SCM changes of V2BP Continuous Build

          Aug 12, 2007 7:53:18 AM hudson.triggers.SCMTrigger$Runner run
          INFO: SCM changes detected in V2BP Continuous Build. Job is already in the queue

          Aug 12, 2007 7:53:18 AM hudson.triggers.SCMTrigger$Runner runPolling
          INFO: Polling SCM changes of V2BP Continuous Build

          Aug 12, 2007 7:52:18 AM hudson.triggers.SCMTrigger$Runner runPolling
          INFO: Polling SCM changes of V2BP Continuous Build

          Aug 12, 2007 7:51:18 AM hudson.triggers.SCMTrigger$Runner runPolling
          INFO: Polling SCM changes of V2BP Continuous Build

          stanoislav added a comment - I'm not able to post comments into #692 so I'm enterign it here. In 128 I still see the issue. On checkin to svn a new build enters a que and this is in the svn pooling log: Started on Aug 12, 2007 7:55:18 AM Revision:103133 (changed from 103128) Done. Took 0 seconds Changes found When the build starts (we have 3 minutes quiet period) immediately another build is added to the queue even that there were no other changes after those that have triggered the build that just started building. The log still shows the same: Started on Aug 12, 2007 7:56:18 AM Revision:103133 (changed from 103128) Done. Took 0 seconds Changes found The full hudson log from that period is here: Aug 12, 2007 7:56:18 AM hudson.triggers.SCMTrigger$Runner run INFO: SCM changes detected in V2BP Continuous Build. Job is already in the queue Aug 12, 2007 7:56:18 AM hudson.triggers.SCMTrigger$Runner runPolling INFO: Polling SCM changes of V2BP Continuous Build Aug 12, 2007 7:55:18 AM hudson.triggers.SCMTrigger$Runner run INFO: SCM changes detected in V2BP Continuous Build. Triggering #2233 Aug 12, 2007 7:55:18 AM hudson.triggers.SCMTrigger$Runner runPolling INFO: Polling SCM changes of V2BP Continuous Build Aug 12, 2007 7:54:18 AM hudson.triggers.SCMTrigger$Runner run INFO: SCM changes detected in V2BP Continuous Build. Triggering #2233 Aug 12, 2007 7:54:18 AM hudson.triggers.SCMTrigger$Runner runPolling INFO: Polling SCM changes of V2BP Continuous Build Aug 12, 2007 7:53:18 AM hudson.triggers.SCMTrigger$Runner run INFO: SCM changes detected in V2BP Continuous Build. Job is already in the queue Aug 12, 2007 7:53:18 AM hudson.triggers.SCMTrigger$Runner runPolling INFO: Polling SCM changes of V2BP Continuous Build Aug 12, 2007 7:52:18 AM hudson.triggers.SCMTrigger$Runner runPolling INFO: Polling SCM changes of V2BP Continuous Build Aug 12, 2007 7:51:18 AM hudson.triggers.SCMTrigger$Runner runPolling INFO: Polling SCM changes of V2BP Continuous Build

            Unassigned Unassigned
            stanoislav stanoislav
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: