[
https://issues.jenkins-ci.org/browse/JENKINS-12888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159543#comment-159543
]
gbois commented on JENKINS-12888:
---------------------------------
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).
> Would like to have fstrigger show what file changed in the build cause
> ----------------------------------------------------------------------
>
> Key: JENKINS-12888
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12888
> Project: Jenkins
> Issue Type: Improvement
> Components: fstrigger
> Reporter: Jim Searle
> Assignee: gbois
> Priority: Minor
>
> 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
