Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-23073

Jobs stop polling for file changes after 1-2 builds

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Component/s: fstrigger-plugin
    • Labels:
      None
    • Environment:
      Master: CentOS 6 virtual machine
      Nodes: a mix of Windows Server 2012 VMs and CentOS 6 VMs
    • Similar Issues:

      Description

      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.

        Attachments

          Activity

            People

            • Assignee:
              gbois Gregory Boissinot
              Reporter:
              mngoldeneagle Jesse Docken
            • Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated: