org.jenkinsci.plugins.fstrigger.FSTriggerException

There are no available Samebug tips for this exception. Do you have an idea how to solve this issue? A short tip would help users who saw this issue last week.

  • Due to SCM change polling not working (log error) on CC Dynamic views, I'm using the FS trigger instead. On startup, as Jenkins looks through jobs, see a few of these in the log SEVERE: Error on trigger startup java.io.FileNotFoundException: /view/foo/vobs/bar/nasty/path.c (No such file or directory) org.jenkinsci.plugins.fstrigger.FSTriggerException: java.io.FileNotFoundException: /view/foo/vobs/bar/nasty/path.c (No such file or directory) at org.jenkinsci.plugins.fstrigger.triggers.FolderContentTrigger.getFileInfo(FolderContentTrigger.java:213) at org.jenkinsci.plugins.fstrigger.triggers.FolderContentTrigger.getFileInfoMaster(FolderContentTrigger.java:146) at org.jenkinsci.plugins.fstrigger.triggers.FolderContentTrigger.getMd5Map(FolderContentTrigger.java:124) at org.jenkinsci.plugins.fstrigger.triggers.FolderContentTrigger.refreshMemoryInfo(FolderContentTrigger.java:100) at org.jenkinsci.plugins.fstrigger.triggers.FolderContentTrigger.start(FolderContentTrigger.java:340) at org.jenkinsci.plugins.fstrigger.triggers.FolderContentTrigger.start(FolderContentTrigger.java:30) at hudson.model.AbstractProject.onLoad(AbstractProject.java:266) at hudson.model.Project.onLoad(Project.java:88) at hudson.model.Items.load(Items.java:115) at jenkins.model.Jenkins$14.run(Jenkins.java:2346) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259) at jenkins.model.Jenkins$5.runTask(Jenkins.java:797) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) Is this a case where the FS trigger should just catch the FNF and log a complaint to its polling log? Also, should the FS triggered jobs fire as early as they do in Jenkins startup, or should Jenkins get far up enough to service the web before activating polling?
    via by Greg Moncreaff,
  • Due to SCM change polling not working (log error) on CC Dynamic views, I'm using the FS trigger instead. On startup, as Jenkins looks through jobs, see a few of these in the log SEVERE: Error on trigger startup java.io.FileNotFoundException: /view/foo/vobs/bar/nasty/path.c (No such file or directory) org.jenkinsci.plugins.fstrigger.FSTriggerException: java.io.FileNotFoundException: /view/foo/vobs/bar/nasty/path.c (No such file or directory) at org.jenkinsci.plugins.fstrigger.triggers.FolderContentTrigger.getFileInfo(FolderContentTrigger.java:213) at org.jenkinsci.plugins.fstrigger.triggers.FolderContentTrigger.getFileInfoMaster(FolderContentTrigger.java:146) at org.jenkinsci.plugins.fstrigger.triggers.FolderContentTrigger.getMd5Map(FolderContentTrigger.java:124) at org.jenkinsci.plugins.fstrigger.triggers.FolderContentTrigger.refreshMemoryInfo(FolderContentTrigger.java:100) at org.jenkinsci.plugins.fstrigger.triggers.FolderContentTrigger.start(FolderContentTrigger.java:340) at org.jenkinsci.plugins.fstrigger.triggers.FolderContentTrigger.start(FolderContentTrigger.java:30) at hudson.model.AbstractProject.onLoad(AbstractProject.java:266) at hudson.model.Project.onLoad(Project.java:88) at hudson.model.Items.load(Items.java:115) at jenkins.model.Jenkins$14.run(Jenkins.java:2346) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259) at jenkins.model.Jenkins$5.runTask(Jenkins.java:797) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) Is this a case where the FS trigger should just catch the FNF and log a complaint to its polling log? Also, should the FS triggered jobs fire as early as they do in Jenkins startup, or should Jenkins get far up enough to service the web before activating polling?
    via by Greg Moncreaff,
    • org.jenkinsci.plugins.fstrigger.FSTriggerException: java.io.FileNotFoundException: /view/foo/vobs/bar
    • asty/path.c (No such file or directory) at org.jenkinsci.plugins.fstrigger.triggers.FolderContentTrigger.getFileInfo(FolderContentTrigger.java:213) at org.jenkinsci.plugins.fstrigger.triggers.FolderContentTrigger.getFileInfoMaster(FolderContentTrigger.java:146) at org.jenkinsci.plugins.fstrigger.triggers.FolderContentTrigger.getMd5Map(FolderContentTrigger.java:124) at org.jenkinsci.plugins.fstrigger.triggers.FolderContentTrigger.refreshMemoryInfo(FolderContentTrigger.java:100) at org.jenkinsci.plugins.fstrigger.triggers.FolderContentTrigger.start(FolderContentTrigger.java:340) at org.jenkinsci.plugins.fstrigger.triggers.FolderContentTrigger.start(FolderContentTrigger.java:30) at hudson.model.AbstractProject.onLoad(AbstractProject.java:266) at hudson.model.Project.onLoad(Project.java:88) at hudson.model.Items.load(Items.java:115) at jenkins.model.Jenkins$14.run(Jenkins.java:2346) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259) at jenkins.model.Jenkins$5.runTask(Jenkins.java:797) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662)
    No Bugmate found.