|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
I'm running into this issue as well.
Below are a bunch of guesses by a novice Jenkins Plugin developer.
Having a look at:
fstrigger-plugin/src/main/java/org/jenkinsci/plugins/fstrigger/triggers/FolderContentTrigger.java
and
xtrigger-lib/src/main/java/org/jenkinsci/lib/xtrigger/AbstractTrigger.java
...it's my *GUESS* that Mr. Boissinot is using the "offlineSlaveOnStartup" member variable to denote that it is the first time that the trigger has been run since the Jenkins Server initialized.
It looks like the "Map<String, FileInfo> md5Map" is just resident in memory and is not saved between sessions. I think it needs to initialize once before the plug-in has a point of reference for future "checkIfModified()" calls.
Suggested solutions going forward:
EASY: Maybe the message should be more descriptive as to what's going on:
"Initilaizing Folder md5Map... Waiting for next schedule to check if there are modifications.");
or
LESS EASY: Initialize the "md5Map" right when Jenkins starts? (instead of waiting for the next scheduled run)
A.K.A. Override: public void start(BuildableItem project, boolean newInstance)???
or
HARD?: The "md5Map" variable should be committed to disk... somehow? and reloaded after a Jenkins Server Reboot.