[JIRA] [configurationslicing] (JENKINS-15934) NPE when trying to open Delete workspace when build is done
vdupain commented on JENKINS-15934 NPE when trying to open Delete workspace when build is done So same issue for me with plugin ws-cleanup 0.16 and configurationslicing 1.37. Method hudson.plugins.ws_cleanup.WsCleanup.getSkipWhenFailed has been removed from WSCleanup plugin since 0.13: https://github.com/jenkinsci/ws-cleanup-plugin/commit/71ee66716f43d046881de857546654a7beea 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/groups/opt_out.
[JIRA] [configurationslicing] (JENKINS-15934) NPE when trying to open Delete workspace when build is done
vdupain edited a comment on JENKINS-15934 NPE when trying to open Delete workspace when build is done So same issue for me with plugin ws-cleanup 0.16 and configurationslicing 1.37: java.lang.NoSuchMethodError: hudson.plugins.ws_cleanup.WsCleanup.getSkipWhenFailed()Z at configurationslicing.wscleanup.CleanupAfterSlicer$CleanupAfterSliceSpec.getCleanupInfo(CleanupAfterSlicer.java:39) at configurationslicing.wscleanup.AbstractWsCleanupSliceSpec.getValues(AbstractWsCleanupSliceSpec.java:50) at configurationslicing.wscleanup.AbstractWsCleanupSliceSpec.getValues(AbstractWsCleanupSliceSpec.java:12) at configurationslicing.UnorderedStringSlicer.accumulate(UnorderedStringSlicer.java:72) at configurationslicing.UnorderedStringSlicer.accumulate(UnorderedStringSlicer.java:6) at configurationslicing.ConfigurationSlicing$SliceExecutor.execute(ConfigurationSlicing.java:125) at configurationslicing.ConfigurationSlicing$SliceExecutor.init(ConfigurationSlicing.java:113) at configurationslicing.ConfigurationSlicing.getDynamic(ConfigurationSlicing.java:98) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java Method hudson.plugins.ws_cleanup.WsCleanup.getSkipWhenFailed has been removed from WSCleanup plugin since 0.13: https://github.com/jenkinsci/ws-cleanup-plugin/commit/71ee66716f43d046881de857546654a7beea 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/groups/opt_out.
[JIRA] [configurationslicing] (JENKINS-15934) NPE when trying to open Delete workspace when build is done
Laurent Denanot commented on JENKINS-15934 NPE when trying to open Delete workspace when build is done Hi, I had the same problem and found an easy cure: Looks like it simply is a case of bad dependency qualification: the NPE is due to the fact that the 'Delete workspace' features depend on the 'ws-cleanup' plugin (https://wiki.jenkins-ci.org/display/JENKINS/Workspace+Cleanup+Plugin) that is listed as an optional dependency of the Configuration Slicing plugin, whereas it really should be listed as a required one... The alternative being adding logic to the Configuration Slicing plugin that automatically detects whether the 'ws-cleanup' plugin is installed and enables or disables the associated 'delete workspace... ' options accordingly. Anyways: Without the 'ws-cleanup' installed : clicking on any of the 'Delete workspace...' links in Configuraiton slicing triggers an NPE. With the 'ws-cleanup' installed: no more NPEs, the configuration pages for the 'Delete workspace...' options get displayed as expected... Hope this helps, Laurent 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/groups/opt_out.
[JIRA] [configurationslicing] (JENKINS-15934) NPE when trying to open Delete workspace when build is done
Laurent Denanot edited a comment on JENKINS-15934 NPE when trying to open Delete workspace when build is done Hi, I had the same problem and found an easy cure: Looks like it simply is a case of bad dependency qualification: the NPE is due to the fact that the 'Delete workspace' features depend on the 'ws-cleanup' plugin (https://wiki.jenkins-ci.org/display/JENKINS/Workspace+Cleanup+Plugin) that is listed as an optional dependency of the Configuration Slicing plugin, whereas it really should be listed as a required one... The alternative being adding logic to the Configuration Slicing plugin that automatically detects whether the 'ws-cleanup' plugin is installed and enables or disables the associated 'delete workspace... ' options accordingly. Anyways: Without the 'ws-cleanup' installed : clicking on any of the 'Delete workspace...' links in Configuraiton slicing triggers an NPE. With the 'ws-cleanup' installed: no more NPEs, the configuration pages for the 'Delete workspace...' options get displayed as expected... Hope this helps, Laurent PS: I'm running Jenkins v 1.512 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/groups/opt_out.
[JIRA] [configurationslicing] (JENKINS-15934) NPE when trying to open Delete workspace when build is done
Laurent Denanot edited a comment on JENKINS-15934 NPE when trying to open Delete workspace when build is done Hi, I had the same problem and found an easy cure: Looks like it simply is a case of bad dependency qualification: the NPE is due to the fact that the 'Delete workspace' features depend on the 'ws-cleanup' plugin (https://wiki.jenkins-ci.org/display/JENKINS/Workspace+Cleanup+Plugin) that is listed as an optional dependency of the Configuration Slicing plugin, whereas it really should be listed as a required one... The alternative being adding logic to the Configuration Slicing plugin that automatically detects whether the 'ws-cleanup' plugin is installed and enables or disables the associated 'delete workspace... ' options accordingly. Anyways: Without the 'ws-cleanup' plugin installed : clicking on any of the 'Delete workspace...' links in Configuraiton slicing triggers an NPE. With the 'ws-cleanup' plugin installed: no more NPEs, the configuration pages for the 'Delete workspace...' options work as expected... Hope this helps, Laurent PS: I'm running Jenkins v 1.512 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/groups/opt_out.
[JIRA] [configurationslicing] (JENKINS-15934) NPE when trying to open Delete workspace when build is done
Laurent Denanot edited a comment on JENKINS-15934 NPE when trying to open Delete workspace when build is done Hi, I had the same problem and found an easy cure: Looks like it simply is a case of bad dependency qualification: the NPE is due to the fact that the 'Delete workspace' features depend on the 'ws-cleanup' (Workspace Cleanup) plugin (https://wiki.jenkins-ci.org/display/JENKINS/Workspace+Cleanup+Plugin) that is listed as an optional dependency of the Configuration Slicing plugin, whereas it really should be listed as a required one... The alternative being adding logic to the Configuration Slicing plugin that automatically detects whether the 'ws-cleanup' plugin is installed and enables or disables the associated 'delete workspace... ' options accordingly. Anyways: Without the 'ws-cleanup' plugin installed : clicking on any of the 'Delete workspace...' links in Configuration slicing triggers an NPE. With the 'ws-cleanup' plugin installed: no more NPEs, the configuration pages for the 'Delete workspace...' options work as expected... Hope this helps, Laurent PS: I'm running Jenkins v 1.512 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/groups/opt_out.
[JIRA] [configurationslicing] (JENKINS-15934) NPE when trying to open Delete workspace when build is done
Laurent Denanot edited a comment on JENKINS-15934 NPE when trying to open Delete workspace when build is done Hi, I had the same problem and found an easy cure: Looks like it simply is a case of bad dependency qualification: the NPE is due to the fact that the 'Delete workspace' features depend on the 'ws-cleanup' (Workspace Cleanup) plugin (see https://wiki.jenkins-ci.org/display/JENKINS/Workspace+Cleanup+Plugin) that is listed as an optional dependency of the Configuration Slicing plugin, whereas it really should be listed as a required one... The alternative being adding logic to the Configuration Slicing plugin that automatically detects whether the 'ws-cleanup' plugin is installed and enables or disables the associated 'delete workspace... ' options accordingly. Anyways: Without the 'ws-cleanup' plugin installed : clicking on any of the 'Delete workspace...' links in Configuration slicing triggers an NPE. With the 'ws-cleanup' plugin installed: no more NPEs, the configuration pages for the 'Delete workspace...' options work as expected... Hope this helps, Laurent PS: I'm running Jenkins v 1.512 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/groups/opt_out.
[JIRA] [configurationslicing] (JENKINS-15934) NPE when trying to open Delete workspace when build is done
Adam Sloan commented on JENKINS-15934 NPE when trying to open Delete workspace when build is done Still, Slicer version 1.36 and Jenkins 1.514 Status Code: 500 Exception: java.lang.NoSuchMethodError: hudson.plugins.ws_cleanup.WsCleanup.getSkipWhenFailed()Z Stacktrace: javax.servlet.ServletException: java.lang.NoSuchMethodError: hudson.plugins.ws_cleanup.WsCleanup.getSkipWhenFailed()Z at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:719) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:384) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:583) at org.kohsuke.stapler.Stapler.service(Stapler.java:214) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at winstone.RequestDispatcher.forward(RequestDispatcher.java:333) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:206) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:179) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:86) at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:84) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:50) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at winstone.RequestDispatcher.forward(RequestDispatcher.java:331) at winstone.RequestHandlerThread.processRequest(RequestHandlerThread.java:227) at winstone.RequestHandlerThread.run(RequestHandlerThread.java:150) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at winstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77) 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) Caused by: java.lang.NoSuchMethodError: hudson.plugins.ws_cleanup.WsCleanup.getSkipWhenFailed()Z at configurationslicing.wscleanup.CleanupAfterSlicer$CleanupAfterSliceSpec.getCleanupInfo(CleanupAfterSlicer.java:39) at configurationslicing.wscleanup.AbstractWsCleanupSliceSpec.getValues(AbstractWsCleanupSliceSpec.java:50) at configurationslicing.wscleanup.AbstractWsCleanupSliceSpec.getValues(AbstractWsCleanupSliceSpec.java:12) at configurationslicing.UnorderedStringSlicer.accumulate(UnorderedStringSlicer.java:72) at configurationslicing.UnorderedStringSlicer.accumulate(UnorderedStringSlicer.java:6) at configurationslicing.ConfigurationSlicing$SliceExecutor.execute(ConfigurationSlicing.java:125) at configurationslicing.ConfigurationSlicing$SliceExecutor.init(ConfigurationSlicing.java:113) at
