You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During Jenkins startup/restart I am always getting an INFO log:
2018-04-03 10:25:09 INFO [hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1 error] Failed to instantiate optional component hudson.plugins.build_timeout.operations.AbortAnd
RestartOperation$DescriptorImpl; skipping
IIRC this happens ever since I installed Jenkins (and I guess this plugin) and now Jenkins version is 2.114 (latest release) and Build Timeout plugin version is 1.19 (latest).
Frankly I think we are not even using this plugin at the moment, but just found this error log irritating and thus at long last dared to file this little issue...
Here is a little bit more Jenkins start-up log context:
2018-04-03 10:25:33 INFO [jenkins.InitReactorRunner$1 onAttained] Started initialization
2018-04-03 10:25:34 INFO [jenkins.InitReactorRunner$1 onAttained] Listed all plugins
2018-04-03 10:25:35 INFO [hudson.plugins.ansicolor.PluginImpl start] AnsiColor: eliminating boring output (https://github.com/jenkinsci/ansicolor-plugin)
2018-04-03 10:25:47 INFO [jenkins.InitReactorRunner$1 onAttained] Prepared all plugins
2018-04-03 10:25:49 INFO [hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1 error] Failed to instantiate optional component hudson.plugins.build_timeout.operations.AbortAnd
RestartOperation$DescriptorImpl; skipping
2018-04-03 10:25:50 INFO [jenkins.InitReactorRunner$1 onAttained] Started all plugins
The text was updated successfully, but these errors were encountered:
During Jenkins startup/restart I am always getting an INFO log:
IIRC this happens ever since I installed Jenkins (and I guess this plugin) and now Jenkins version is 2.114 (latest release) and Build Timeout plugin version is 1.19 (latest).
Frankly I think we are not even using this plugin at the moment, but just found this error log irritating and thus at long last dared to file this little issue...
Here is a little bit more Jenkins start-up log context:
The text was updated successfully, but these errors were encountered: