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

FSTrigger triggers builds on jenkins restart

    XMLWordPrintable

Details

    Description

      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.

      Attachments

        Activity

          Code changed in jenkins
          User: Gregory Boissinot
          Path:
          src/main/java/org/jenkinsci/plugins/fstrigger/triggers/FileNameTrigger.java
          http://jenkins-ci.org/commit/fstrigger-plugin/132a6a6a2631adafd4de12173ceafa5040fdc82f
          Log:
          Fix JENKINS-12924

          scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Gregory Boissinot Path: src/main/java/org/jenkinsci/plugins/fstrigger/triggers/FileNameTrigger.java http://jenkins-ci.org/commit/fstrigger-plugin/132a6a6a2631adafd4de12173ceafa5040fdc82f Log: Fix JENKINS-12924
          jimsearle Jim Searle added a comment - - edited

          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.

          jimsearle Jim Searle added a comment - - edited 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.

          Code changed in jenkins
          User: Gregory Boissinot
          Path:
          pom.xml
          src/main/java/org/jenkinsci/plugins/fstrigger/triggers/FileNameTrigger.java
          http://jenkins-ci.org/commit/fstrigger-plugin/9ff1c5f813efa172812985bfcebf68bd1cb4ac11
          Log:
          Fix JENKINS-12924

          scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Gregory Boissinot Path: pom.xml src/main/java/org/jenkinsci/plugins/fstrigger/triggers/FileNameTrigger.java http://jenkins-ci.org/commit/fstrigger-plugin/9ff1c5f813efa172812985bfcebf68bd1cb4ac11 Log: Fix JENKINS-12924

          Happens also on latest Jenkins: 1.504, with FSTrigger: 0.35

          dumghen Ghenadie Dumitru added a comment - Happens also on latest Jenkins: 1.504, with FSTrigger: 0.35

          @Ghenadie Do you have the ability to isolate the issue?
          I'd to reproduce it in my environment.
          Thanks

          gbois Gregory Boissinot added a comment - @Ghenadie Do you have the ability to isolate the issue? I'd to reproduce it in my environment. Thanks

          Hi,

          The issue was isolated.
          It happens every time the Master is restarted (Jenkins master is started under Tomcat) and master has a number of slaves connected through SSH on different machines: all machines (master+slave) are CentOS.
          I have configured few jobs on each master, jobs are tied to specific slaves. On some slaves, jobs are triggered to run as described in issue once the master is restarted. Not on all slaves, which is little weird.

          dumghen Ghenadie Dumitru added a comment - Hi, The issue was isolated. It happens every time the Master is restarted (Jenkins master is started under Tomcat) and master has a number of slaves connected through SSH on different machines: all machines (master+slave) are CentOS. I have configured few jobs on each master, jobs are tied to specific slaves. On some slaves, jobs are triggered to run as described in issue once the master is restarted. Not on all slaves, which is little weird.

          People

            gbois Gregory Boissinot
            jimsearle Jim Searle
            Votes:
            3 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated: