• Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • other
    • None
    • Platform: All, OS: All

      We have upgraded from Hudson 1.224 to 1.244.
      We had projects set to a quiet period of 2 minutes. And we have svn update
      polling every minute.

      We kept this configuration, but this caused the builder not to build at all. It
      kept the job in the queue for every. It got reset every time (also without
      check-ins).
      We had to remove the quiet period to get it building.

          [JENKINS-2180] Quiet period keeps running without building

          adrian_ added a comment -

          @mdonohue

          You are right. I removed it.

          adrian_ added a comment - @mdonohue You are right. I removed it.

          Alan Harder added a comment -

          Marking as resolved again, now that subversion plugin 1.12 has been released.

          Alan Harder added a comment - Marking as resolved again, now that subversion plugin 1.12 has been released.

          I'm seeing this issue - or something very like it with CVS on Jenkins version 1.414, CVS Plugin 1.4

          I had polling turned on in my CI projects but with a blank poll schedule. I wanted to enable polling but not actually do it. Once I realized what was going on, I set the polling schedule to once a day but still saw this behavior. Even tried restarting Jenkins in the hopes that it would clear any cobwebs or old polling threads with a bad schedule, but still saw the behavior.
          It didn't resolve until I disabled polling altogether.

          G. Ann Campbell added a comment - I'm seeing this issue - or something very like it with CVS on Jenkins version 1.414, CVS Plugin 1.4 I had polling turned on in my CI projects but with a blank poll schedule. I wanted to enable polling but not actually do it. Once I realized what was going on, I set the polling schedule to once a day but still saw this behavior. Even tried restarting Jenkins in the hopes that it would clear any cobwebs or old polling threads with a bad schedule, but still saw the behavior. It didn't resolve until I disabled polling altogether.

          Sorry if you get this twice - I just posted to the issue before re-opening. I am seeing this behavior on Jenkins 1.414 & CVS plugin 1.4.

          I merely had polling enabled in the CI jobs, but with no schedule & a 5-min. quiet period. Jobs would tick down the quiet period to just under a minute, then reset. Checking the access logs showed no additional CI triggers.

          Setting a daily poll cron still didn't help. I finally disabled polling altogether & finally saw jobs finishing their quiet periods and building.

          I'll be happy to provide whatever system information you need.

          G. Ann Campbell added a comment - Sorry if you get this twice - I just posted to the issue before re-opening. I am seeing this behavior on Jenkins 1.414 & CVS plugin 1.4. I merely had polling enabled in the CI jobs, but with no schedule & a 5-min. quiet period. Jobs would tick down the quiet period to just under a minute, then reset. Checking the access logs showed no additional CI triggers. Setting a daily poll cron still didn't help. I finally disabled polling altogether & finally saw jobs finishing their quiet periods and building. I'll be happy to provide whatever system information you need.

          Alan Harder added a comment -

          This was a long running issue and I'd rather not see it reopened. I believe the problem is the newer polling API was implemented for subversion plugin but probably not for CVS. Please file a new feature request asking for new polling API support in CVS plugin, thanks!

          Alan Harder added a comment - This was a long running issue and I'd rather not see it reopened. I believe the problem is the newer polling API was implemented for subversion plugin but probably not for CVS. Please file a new feature request asking for new polling API support in CVS plugin, thanks!

          I'm still seeing this issue using Jenkins 1.596.2 and Subversion plugin 2.5.
          Quiet period is set to 900 seconds, SCM polling is done every minute.
          Jenkins is always showing "(pending—In the quiet period. Expires in 14 min)".

          Am I doing something wrong?

          Patric Rufflar added a comment - I'm still seeing this issue using Jenkins 1.596.2 and Subversion plugin 2.5. Quiet period is set to 900 seconds, SCM polling is done every minute. Jenkins is always showing "(pending—In the quiet period. Expires in 14 min)". Am I doing something wrong?

          Daniel Beck added a comment -

          mineralwasser:

          Am I doing something wrong?

          I see the same issue (on 1.565.3 as well). Please file a new issue about this against the core component and assign it to me, I'll look into it.

          Daniel Beck added a comment - mineralwasser : Am I doing something wrong? I see the same issue (on 1.565.3 as well). Please file a new issue about this against the core component and assign it to me, I'll look into it.

          Code changed in jenkins
          User: Daniel Beck
          Path:
          core/src/main/java/hudson/model/Queue.java
          http://jenkins-ci.org/commit/jenkins/1072f5c1372d2884beb07c9114b9b90ce0bf037e
          Log:
          JENKINS-2180 Always use earlier scheduling date.

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Daniel Beck Path: core/src/main/java/hudson/model/Queue.java http://jenkins-ci.org/commit/jenkins/1072f5c1372d2884beb07c9114b9b90ce0bf037e Log: JENKINS-2180 Always use earlier scheduling date.

          Code changed in jenkins
          User: Daniel Beck
          Path:
          core/src/main/java/hudson/model/Queue.java
          http://jenkins-ci.org/commit/jenkins/c9c62d3681460d4898f26e8fe07b9d4fc80f40e7
          Log:
          Merge pull request #1665 from daniel-beck/JENKINS-2180

          JENKINS-2180 Always use earlier scheduling date.

          Compare: https://github.com/jenkinsci/jenkins/compare/8c5b9cd008a4...c9c62d368146

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Daniel Beck Path: core/src/main/java/hudson/model/Queue.java http://jenkins-ci.org/commit/jenkins/c9c62d3681460d4898f26e8fe07b9d4fc80f40e7 Log: Merge pull request #1665 from daniel-beck/ JENKINS-2180 JENKINS-2180 Always use earlier scheduling date. Compare: https://github.com/jenkinsci/jenkins/compare/8c5b9cd008a4...c9c62d368146

          dogfood added a comment -

          Integrated in jenkins_main_trunk #4189
          JENKINS-2180 Always use earlier scheduling date. (Revision 1072f5c1372d2884beb07c9114b9b90ce0bf037e)

          Result = UNSTABLE
          daniel-beck : 1072f5c1372d2884beb07c9114b9b90ce0bf037e
          Files :

          • core/src/main/java/hudson/model/Queue.java

          dogfood added a comment - Integrated in jenkins_main_trunk #4189 JENKINS-2180 Always use earlier scheduling date. (Revision 1072f5c1372d2884beb07c9114b9b90ce0bf037e) Result = UNSTABLE daniel-beck : 1072f5c1372d2884beb07c9114b9b90ce0bf037e Files : core/src/main/java/hudson/model/Queue.java

            kohsuke Kohsuke Kawaguchi
            cbos Cees Bos
            Votes:
            19 Vote for this issue
            Watchers:
            10 Start watching this issue

              Created:
              Updated:
              Resolved: