-
Bug
-
Resolution: Fixed
-
Major
-
None
-
Jenkins v1.501, Latest FSTrigger, Envinject Plugins, CentOS 5.5, JDK 1.7_07
Restarting Tomcat. During the restart process Jenkins fails to load jobs which use the "FSTrigger" plugin (see stacktrace1.txt). Some jobs are displayed in Jenkins (set-"A"), some no longer show up (set-"B"), but are still present on the disk. Changing a job-configuration of set-"A" jobs results in a 500-Error with stacktrace. The FSTrigger functionality for set-"A" jobs no longer works (changing the content of a monitored folder does not trigger the job). The Envinject Plugin is not used by the jobs. If the Jenkins configuration is reloaded from disk through the browser, then set-"A" jobs are gone too.
