[JENKINS-24244] Scheduled polling not run

Type: Bug
Resolution: Not A Defect
Priority: Major
Component/s: core
Labels:
- cron

Similar Issues:
Powered by SuggestiMate

Show

Mercurial scm polling stops after running once after restart.
Jenkins version: 1.570 (can only choose 'current' in Jira)

config.xml scm:

<scm class="hudson.plugins.mercurial.MercurialSCM" plugin="mercurial@1.50">
    <installation>(Default)</installation>
    <source>http://host/path/project</source>
    <modules/>
    <revisionType>BRANCH</revisionType>
    <revision>stable</revision>
    <clean>true</clean>
    <browser class="hudson.plugins.mercurial.browser.HgWeb">
        <url>http://host/path/project/</url>
    </browser>
    <credentialsId/>
    <disableChangeLog>false</disableChangeLog>
</scm>

config.xml triggers:

<triggers>
    <hudson.triggers.SCMTrigger>
        <spec>H 3 * * 1-6</spec>
        <ignorePostCommitHooks>false</ignorePostCommitHooks>
    </hudson.triggers.SCMTrigger>
</triggers>

scm-polling.log (today is 14-aug-2014, so it did not run for a couple of days already):

Started on 9-aug-2014 3:27:01
Polling SCM changes on master
[workspace] $ hg pull --rev stable
pulling from http://host/path/project
no changes found
[workspace] $ hg log --rev stable --template {node}
[workspace] $ hg log --rev stable --template {rev}
Done. Took 1,3 seconden
No changes

depends on

JENKINS-22431 Rewrite Trigger.Cron to be an AperiodicWork

Open

is related to

JENKINS-26208 Jenkins should not skip polling while quieting down

Resolved

Rick Oosterholt created issue - 2014-08-13 11:58

Rick Oosterholt made changes - 2014-08-13 12:06

Description	Original: Mercurial scm polling stops after running once after restart. config.xml scm: {code:xml} <scm class="hudson.plugins.mercurial.MercurialSCM" plugin="mercurial@1.50"> <installation>(Default)</installation> <source>http://host/path/project</source> <modules/> <revisionType>BRANCH</revisionType> <revision>stable</revision> <clean>true</clean> <browser class="hudson.plugins.mercurial.browser.HgWeb"> <url>http://host/path/project/</url> </browser> <credentialsId/> <disableChangeLog>false</disableChangeLog> </scm> {code} triggers: {code:xml} <triggers> <hudson.triggers.SCMTrigger> <spec>H 3 * * 1-6</spec> <ignorePostCommitHooks>false</ignorePostCommitHooks> </hudson.triggers.SCMTrigger> </triggers> {code}	New: Mercurial scm polling stops after running once after restart. config.xml scm: {code:xml} <scm class="hudson.plugins.mercurial.MercurialSCM" plugin="mercurial@1.50"> <installation>(Default)</installation> <source>http://host/path/project</source> <modules/> <revisionType>BRANCH</revisionType> <revision>stable</revision> <clean>true</clean> <browser class="hudson.plugins.mercurial.browser.HgWeb"> <url>http://host/path/project/</url> </browser> <credentialsId/> <disableChangeLog>false</disableChangeLog> </scm> {code} config.xml triggers: {code:xml} <triggers> <hudson.triggers.SCMTrigger> <spec>H 3 * * 1-6</spec> <ignorePostCommitHooks>false</ignorePostCommitHooks> </hudson.triggers.SCMTrigger> </triggers> {code} scm-polling.log: {code} Started on 9-aug-2014 3:27:01 Polling SCM changes on master [workspace] $ hg pull --rev stable pulling from http://host/path/project no changes found [workspace] $ hg log --rev stable --template {node} [workspace] $ hg log --rev stable --template {rev} Done. Took 1,3 seconden No changes {code}
Summary	Original: Polling of Mercurial scm stop working	New: Polling of Mercurial scm stoped working

Rick Oosterholt made changes - 2014-08-13 12:08

Description

Original: Mercurial scm polling stops after running once after restart.

config.xml scm:
{code:xml}
<scm class="hudson.plugins.mercurial.MercurialSCM" plugin="mercurial@1.50">
    <installation>(Default)</installation>
    <source>http://host/path/project</source>
    <modules/>
    <revisionType>BRANCH</revisionType>
    <revision>stable</revision>
    <clean>true</clean>
    <browser class="hudson.plugins.mercurial.browser.HgWeb">
        <url>http://host/path/project/</url>
    </browser>
    <credentialsId/>
    <disableChangeLog>false</disableChangeLog>
</scm>
{code}

config.xml triggers:
{code:xml}
<triggers>
    <hudson.triggers.SCMTrigger>
        <spec>H 3 * * 1-6</spec>
        <ignorePostCommitHooks>false</ignorePostCommitHooks>
    </hudson.triggers.SCMTrigger>
</triggers>
{code}

scm-polling.log:
{code}
Started on 9-aug-2014 3:27:01
Polling SCM changes on master
[workspace] $ hg pull --rev stable
pulling from http://host/path/project
no changes found
[workspace] $ hg log --rev stable --template {node}
[workspace] $ hg log --rev stable --template {rev}
Done. Took 1,3 seconden
No changes
{code}

New: Mercurial scm polling stops after running once after restart.

config.xml scm:
{code:xml}
<scm class="hudson.plugins.mercurial.MercurialSCM" plugin="mercurial@1.50">
    <installation>(Default)</installation>
    <source>http://host/path/project</source>
    <modules/>
    <revisionType>BRANCH</revisionType>
    <revision>stable</revision>
    <clean>true</clean>
    <browser class="hudson.plugins.mercurial.browser.HgWeb">
        <url>http://host/path/project/</url>
    </browser>
    <credentialsId/>
    <disableChangeLog>false</disableChangeLog>
</scm>
{code}

config.xml triggers:
{code:xml}
<triggers>
    <hudson.triggers.SCMTrigger>
        <spec>H 3 * * 1-6</spec>
        <ignorePostCommitHooks>false</ignorePostCommitHooks>
    </hudson.triggers.SCMTrigger>
</triggers>
{code}

scm-polling.log (today is 14-aug-2014, so it did not run for a couple of days already):
{code}
Started on 9-aug-2014 3:27:01
Polling SCM changes on master
[workspace] $ hg pull --rev stable
pulling from http://host/path/project
no changes found
[workspace] $ hg log --rev stable --template {node}
[workspace] $ hg log --rev stable --template {rev}
Done. Took 1,3 seconden
No changes
{code}

Rick Oosterholt made changes - 2014-08-13 12:09

Description

Original: Mercurial scm polling stops after running once after restart.

config.xml scm:
{code:xml}
<scm class="hudson.plugins.mercurial.MercurialSCM" plugin="mercurial@1.50">
    <installation>(Default)</installation>
    <source>http://host/path/project</source>
    <modules/>
    <revisionType>BRANCH</revisionType>
    <revision>stable</revision>
    <clean>true</clean>
    <browser class="hudson.plugins.mercurial.browser.HgWeb">
        <url>http://host/path/project/</url>
    </browser>
    <credentialsId/>
    <disableChangeLog>false</disableChangeLog>
</scm>
{code}

config.xml triggers:
{code:xml}
<triggers>
    <hudson.triggers.SCMTrigger>
        <spec>H 3 * * 1-6</spec>
        <ignorePostCommitHooks>false</ignorePostCommitHooks>
    </hudson.triggers.SCMTrigger>
</triggers>
{code}

scm-polling.log (today is 14-aug-2014, so it did not run for a couple of days already):
{code}
Started on 9-aug-2014 3:27:01
Polling SCM changes on master
[workspace] $ hg pull --rev stable
pulling from http://host/path/project
no changes found
[workspace] $ hg log --rev stable --template {node}
[workspace] $ hg log --rev stable --template {rev}
Done. Took 1,3 seconden
No changes
{code}

New: Mercurial scm polling stops after running once after restart.
Jenkins version: 1.570 (can only choose 'current' in Jira)

config.xml scm:
{code:xml}
<scm class="hudson.plugins.mercurial.MercurialSCM" plugin="mercurial@1.50">
    <installation>(Default)</installation>
    <source>http://host/path/project</source>
    <modules/>
    <revisionType>BRANCH</revisionType>
    <revision>stable</revision>
    <clean>true</clean>
    <browser class="hudson.plugins.mercurial.browser.HgWeb">
        <url>http://host/path/project/</url>
    </browser>
    <credentialsId/>
    <disableChangeLog>false</disableChangeLog>
</scm>
{code}

config.xml triggers:
{code:xml}
<triggers>
    <hudson.triggers.SCMTrigger>
        <spec>H 3 * * 1-6</spec>
        <ignorePostCommitHooks>false</ignorePostCommitHooks>
    </hudson.triggers.SCMTrigger>
</triggers>
{code}

scm-polling.log (today is 14-aug-2014, so it did not run for a couple of days already):
{code}
Started on 9-aug-2014 3:27:01
Polling SCM changes on master
[workspace] $ hg pull --rev stable
pulling from http://host/path/project
no changes found
[workspace] $ hg log --rev stable --template {node}
[workspace] $ hg log --rev stable --template {rev}
Done. Took 1,3 seconden
No changes
{code}

Jesse Glick added a comment - 2014-08-18 16:16

Without information to reproduce it is hard to say what is at fault. Did polling not get triggered at all? Are you using version 1.50 of the plugin, or 1.51-beta-2 (on experimental update center) that has special integration with 1.568+? Seems like you are not using caching. Does polling work for other SCMs?

Just checked 1.570 with 1.50 on Linux and polling is working fine (against a Bitbucket test repo) even after a restart.

Jesse Glick added a comment - 2014-08-18 16:16 Without information to reproduce it is hard to say what is at fault. Did polling not get triggered at all? Are you using version 1.50 of the plugin, or 1.51-beta-2 (on experimental update center) that has special integration with 1.568+? Seems like you are not using caching. Does polling work for other SCMs? Just checked 1.570 with 1.50 on Linux and polling is working fine (against a Bitbucket test repo) even after a restart.

Jesse Glick made changes - 2014-08-18 16:16

Resolution		New: Incomplete [ 4 ]
Status	Original: Open [ 1 ]	New: Resolved [ 5 ]

Rick Oosterholt added a comment - 2014-08-19 07:02

Well, instead of marking this issue at resolved, you could have just asked for more info. That is the reason I posted this issue; though the community/maintainers would request more info when needed or guide a user to get some...

here's the requested info:
Polling used to work just fine. We have lots of other build which still work fine. As stated, the polling runs only once after restart of Jenkins.
The plugin version is 1.50.
We are only using Mercurial, so I cannot say whether or not other SCMs do work.

Seems like you are not using caching.

Not sure what you mean, were can I check this.

If you or others need any more info or guide me to get logging or something, I would be more than happy to provide it.

Rick Oosterholt added a comment - 2014-08-19 07:02 Well, instead of marking this issue at resolved, you could have just asked for more info. That is the reason I posted this issue; though the community/maintainers would request more info when needed or guide a user to get some... here's the requested info: Polling used to work just fine. We have lots of other build which still work fine. As stated, the polling runs only once after restart of Jenkins. The plugin version is 1.50. We are only using Mercurial, so I cannot say whether or not other SCMs do work. Seems like you are not using caching. Not sure what you mean, were can I check this. If you or others need any more info or guide me to get logging or something, I would be more than happy to provide it.

Rick Oosterholt made changes - 2014-08-19 07:03

Resolution	Original: Incomplete [ 4 ]
Status	Original: Resolved [ 5 ]	New: Reopened [ 4 ]

Jesse Glick added a comment - 2014-08-19 13:52

Resolved/Incomplete includes the state of waiting for more information. There is an open proposal to add a dedicated status for this purpose to this JIRA instance, in which case Incomplete could be reserved for abandoned issues, but that does not seem to have been implemented yet. There needs to be some mechanism for differentiating acknowledged open bugs, from conversations that may or may not be a real bug in some component or another (i.e., support requests).

I would start by adding a logger recording hudson.triggers.SCMTrigger and hudson.triggers.Trigger at fine levels, checking $JENKINS_HOME/scm-polling.log, and generally checking log files for errors. If that turns up nothing special, use a debugger.

Jesse Glick added a comment - 2014-08-19 13:52 Resolved/Incomplete includes the state of waiting for more information. There is an open proposal to add a dedicated status for this purpose to this JIRA instance, in which case Incomplete could be reserved for abandoned issues, but that does not seem to have been implemented yet. There needs to be some mechanism for differentiating acknowledged open bugs, from conversations that may or may not be a real bug in some component or another (i.e., support requests). I would start by adding a logger recording hudson.triggers.SCMTrigger and hudson.triggers.Trigger at fine levels, checking $JENKINS_HOME/scm-polling.log , and generally checking log files for errors. If that turns up nothing special, use a debugger.

Jesse Glick made changes - 2014-08-19 13:52

Resolution		New: Incomplete [ 4 ]
Status	Original: Reopened [ 4 ]	New: Resolved [ 5 ]

Assignee:: Unassigned

Reporter:: Rick Oosterholt

Votes:: 0 Vote for this issue

Watchers:: 3 Start watching this issue

Created:: 2014-08-13 11:58

Updated:: 2014-12-23 10:42

Resolved:: 2014-08-21 11:57

Jenkins

Details

Description

Attachments

Issue Links

Activity

Collapse comment: Jesse Glick added a comment - 2014-08-18 16:16

Expand comment: Jesse Glick added a comment - 2014-08-18 16:16

Collapse comment: Rick Oosterholt added a comment - 2014-08-19 07:02

Expand comment: Rick Oosterholt added a comment - 2014-08-19 07:02

Collapse comment: Jesse Glick added a comment - 2014-08-19 13:52

Expand comment: Jesse Glick added a comment - 2014-08-19 13:52

People

Dates