The FSTrigger plugin is great. However, as far as I can tell, it is missing one major feature – I dont see a way for it to tell my job why it is triggering. (ie what file(s) are new).
This is a pretty important bit of functionality, since a very important usage of this plugin is for a drop directory, and when one has a drop directory, one needs to know what has changed. (so those files can be updated). This then requires logic to figure out what had changed from the previous run. (which I presume the FSTrigger plugin already knows).
It would be super-handy if the FSTrigger plugin exposed some environment variables telling the job what had changed. (why it is triggering)