• Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • fstrigger-plugin
    • None

      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.

          [JENKINS-12924] FSTrigger triggers builds on jenkins restart

          Jim Searle created issue -

          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/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
          Gregory Boissinot made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]

          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.

          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.
          Jim Searle made changes -
          Resolution Original: Fixed [ 1 ]
          Status Original: Resolved [ 5 ] New: Reopened [ 4 ]

          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/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
          Gregory Boissinot made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: Reopened [ 4 ] New: Resolved [ 5 ]

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

          Ghenadie Dumitru added a comment - Happens also on latest Jenkins: 1.504, with FSTrigger: 0.35
          Ghenadie Dumitru made changes -
          Resolution Original: Fixed [ 1 ]
          Status Original: Resolved [ 5 ] New: Reopened [ 4 ]

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

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

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

              Created:
              Updated: