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

Would like to have fstrigger show what file changed in the build cause

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Minor Minor
    • fstrigger-plugin
    • None

      I have a job that monitors a few files, currently fstrigger sets the build cause to:
      [FSTrigger] Triggered by a change to a file
      It would be nice if it said which file actually changed.

          [JENKINS-12888] Would like to have fstrigger show what file changed in the build cause

          You're right.
          It's a known and big issue.

          FSTrigger belongs to the X-Trigger typology through XTrigger plugin.
          XTrigger plugin enables you to poll changes from an environment which can be a filesystem, a build result, a binary repository and so on.
          Having a complete diff in order to have a change log as you have for a SCM polling is very difficult.
          We have difficulty providing that because we don't have any way to lock a state such as a tag (label, baseline, ...) in SCMs.

          In a first time, I'll provide the change log (the reason that have scheduled the build).

          Gregory Boissinot added a comment - You're right. It's a known and big issue. FSTrigger belongs to the X-Trigger typology through XTrigger plugin. XTrigger plugin enables you to poll changes from an environment which can be a filesystem, a build result, a binary repository and so on. Having a complete diff in order to have a change log as you have for a SCM polling is very difficult. We have difficulty providing that because we don't have any way to lock a state such as a tag (label, baseline, ...) in SCMs. In a first time, I'll provide the change log (the reason that have scheduled the build).

          Code changed in jenkins
          User: Gregory Boissinot
          Path:
          src/main/java/org/jenkinsci/lib/xtrigger/AbstractTrigger.java
          src/main/java/org/jenkinsci/lib/xtrigger/AbstractTriggerByFullContext.java
          src/main/java/org/jenkinsci/lib/xtrigger/XTriggerCause.java
          src/main/java/org/jenkinsci/lib/xtrigger/XTriggerCauseAction.java
          src/main/java/org/jenkinsci/lib/xtrigger/XTriggerContext.java
          src/main/resources/org/jenkinsci/lib/xtrigger/XTriggerCauseAction/index.jelly
          http://jenkins-ci.org/commit/xtrigger-lib/ed9a90b62e507005b471c54a27da51a1de6d468c
          Log:
          Fix JENKINS-12888

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Gregory Boissinot Path: src/main/java/org/jenkinsci/lib/xtrigger/AbstractTrigger.java src/main/java/org/jenkinsci/lib/xtrigger/AbstractTriggerByFullContext.java src/main/java/org/jenkinsci/lib/xtrigger/XTriggerCause.java src/main/java/org/jenkinsci/lib/xtrigger/XTriggerCauseAction.java src/main/java/org/jenkinsci/lib/xtrigger/XTriggerContext.java src/main/resources/org/jenkinsci/lib/xtrigger/XTriggerCauseAction/index.jelly http://jenkins-ci.org/commit/xtrigger-lib/ed9a90b62e507005b471c54a27da51a1de6d468c Log: Fix JENKINS-12888

          Fix in FSTrigger 0.28
          All other typologies are updated too.

          Gregory Boissinot added a comment - Fix in FSTrigger 0.28 All other typologies are updated too.

          Jim Searle added a comment -

          Thanks! I'll check this out today.

          Jim Searle added a comment - Thanks! I'll check this out today.

          Is it possible to use the path or name of the file which has triggered the job as a parameter later in the same job? Is there any environmental variable with this info provided by FSTrigger or any other plugin?

          Szabolcs Sélley added a comment - Is it possible to use the path or name of the file which has triggered the job as a parameter later in the same job? Is there any environmental variable with this info provided by FSTrigger or any other plugin?

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

              Created:
              Updated:
              Resolved: