[
https://issues.jenkins-ci.org/browse/JENKINS-12924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159978#comment-159978
]
Jim Searle edited comment on JENKINS-12924 at 3/8/12 12:27 AM:
---------------------------------------------------------------
This is with version 0.29:
Polling started on Mar 7, 2012 4:16:51 PM
Polling for the job ...
Searching a node to run the polling for the label '...'.
Polling remotely on ...
Checking one file: '...'.
Slave(s) were offline at startup. Waiting for next schedule to check if there
are modifications.
Checking one file: '...'.
The file didn't exist for the previous polling and now it exists.
Polling complete. Took 0.7 sec.
Changes found. Scheduling a build.
was (Author: jimsearle):
Polling started on Mar 7, 2012 4:16:51 PM
Polling for the job ...
Searching a node to run the polling for the label '...'.
Polling remotely on ...
Checking one file: '...'.
Slave(s) were offline at startup. Waiting for next schedule to check if there
are modifications.
Checking one file: '...'.
The file didn't exist for the previous polling and now it exists.
Polling complete. Took 0.7 sec.
Changes found. Scheduling a build.
> FSTrigger triggers builds on jenkins restart
> --------------------------------------------
>
> Key: JENKINS-12924
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12924
> Project: Jenkins
> Issue Type: Bug
> Components: fstrigger
> Reporter: Jim Searle
> Assignee: gbois
>
> I'm using FSTrigger 0.28, when I restart jenkins it kicked off all my jobs
> that were previously built. The log says:
> The file didn't exist for the previous polling and now it exists.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
