-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
Master: CentOS 6 virtual machine
Nodes: a mix of Windows Server 2012 VMs and CentOS 6 VMs
I have several jobs configured in my Jenkins instance that are set up to poll a network share for the existence of a specific file, which will trigger a build (which will delete the file once it starts). This setup has been working well for many months, but starting about a week ago the fstrigger plugin inexplicably stopped polling. Accessing the fstrigger log in the job yields the message:
"Polling has not run yet."
Even though polling is set to occur every minute in each job. Restarting Jenkins temporarily resolves the issue, but once the job has been triggered once or twice polling invariably stops again. Jenkins logs do not show any exceptions or noteworthy information.
[JENKINS-23073] Jobs stop polling for file changes after 1-2 builds
Alec Matschiner
added a comment - Is there any update on this issue? I'm having an issue with a job that uses a script to trigger a build, and it was working fop a while, then all of a sudden seems to stop polling. There is no information in the Script Trigger log other than "Polling has not run yet." Is there a fix for this, a work around, or even a way to produce more log info to help debug?
Alec Matschiner
added a comment - Is there any update on this issue? I'm having an issue with a job that uses a script to trigger a build, and it was working fop a while, then all of a sudden seems to stop polling. There is no information in the Script Trigger log other than "Polling has not run yet." Is there a fix for this, a work around, or even a way to produce more log info to help debug? 
I have met the same problem in [ScriptTrigger] - Poll with a shell or batch script
Polling has not run yet.