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

[FSTrigger] - Monitor files - Does not monitor a unix soft link

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Critical Critical
    • fstrigger-plugin
    • None
    • UNIX

      [FSTrigger] - Monitor files - Does not check the date/time modified of a UNIX softlink.

          [JENKINS-12168] [FSTrigger] - Monitor files - Does not monitor a unix soft link

          Jim Searle created issue -

          Jim Searle added a comment -

          I tested this a little more and found that if the soft link is changed then the job is not triggered, but if the file pointed to by the soft link changes the job is triggered.

          We would like it to be triggered in both cases.

          Jim Searle added a comment - I tested this a little more and found that if the soft link is changed then the job is not triggered, but if the file pointed to by the soft link changes the job is triggered. We would like it to be triggered in both cases.

          Gregory Boissinot added a comment - - edited

          Please could you tell me what do you mean about updating the soft link (executing a command, ...)?

          Gregory Boissinot added a comment - - edited Please could you tell me what do you mean about updating the soft link (executing a command, ...)?

          Jim Searle added a comment -

          If the object being monitored is a soft link:
          somefile -> file1
          then if the link is modified with:
          rm -f somefile ; ln -s file2 somefile
          then FSTrigger does not trigger a build unless file2 is newer than file1. In our case, it should trigger the job whenever the link is modified.

          Jim Searle added a comment - If the object being monitored is a soft link: somefile -> file1 then if the link is modified with: rm -f somefile ; ln -s file2 somefile then FSTrigger does not trigger a build unless file2 is newer than file1. In our case, it should trigger the job whenever the link is modified.

          SCM/JIRA link daemon added a comment -

          Code changed in jenkins
          User: Gregory Boissinot
          Path:
          src/main/java/org/jenkinsci/plugins/fstrigger/triggers/FolderContentTrigger.java
          http://jenkins-ci.org/commit/fstrigger-plugin/24fae7a25974c84f33208603f8a935e197193390
          Log:
          Fix JENKINS-12168

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Gregory Boissinot Path: src/main/java/org/jenkinsci/plugins/fstrigger/triggers/FolderContentTrigger.java http://jenkins-ci.org/commit/fstrigger-plugin/24fae7a25974c84f33208603f8a935e197193390 Log: Fix JENKINS-12168

          Gregory Boissinot added a comment -

          I found a solution: if the slink has changed, the build is triggered.
          Please could you upgrade to FStrigger 0.22?
          Thanks

          Gregory Boissinot added a comment - I found a solution: if the slink has changed, the build is triggered. Please could you upgrade to FStrigger 0.22? Thanks
          Gregory Boissinot made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 142490 ] New: JNJira + In-Review [ 190130 ]

            gbois Gregory Boissinot
            jimsearle Jim Searle
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: