-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
Jenkins LTS 2.60.3
Periodic Reincarnation Plugin updated to 1.11 on 23rd of August 2017
a lot of other plugins
After upgrading our instance yesterday some builds of jobs got stuck after they obviously finished with all build steps.
Last console output of builds have been:
Finished Calculation of disk usage of workspace in 0 seconds
which stems from the Disk-Usage Plugin.
Watching the corresponding threads with the Monitoring plugin I could see this similar stacktrace at all build threads:
Executor #13 for NODENAME : executing JOB_NAME #BUILDNUMBER java.util.Collections$UnmodifiableCollection$1.hasNext(Collections.java:1041) java.util.Collections$UnmodifiableCollection$1.hasNext(Collections.java:1041) hudson.model.Run.getCause(Run.java:582) org.jenkinsci.plugins.periodicreincarnation.AfterbuildReincarnation.checkRestartDepth(AfterbuildReincarnation.java:185) org.jenkinsci.plugins.periodicreincarnation.AfterbuildReincarnation.noChangeRestart(AfterbuildReincarnation.java:107) org.jenkinsci.plugins.periodicreincarnation.AfterbuildReincarnation.onCompleted(AfterbuildReincarnation.java:70) org.jenkinsci.plugins.periodicreincarnation.AfterbuildReincarnation.onCompleted(AfterbuildReincarnation.java:18) hudson.model.listeners.RunListener.fireCompleted(RunListener.java:211) hudson.model.Run.execute(Run.java:1780) hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) hudson.model.ResourceController.execute(ResourceController.java:97) hudson.model.Executor.run(Executor.java:405)
Find attached the global configuration of the periodic reincarnation plugin in our instance. The jobs do not have a local configuration.
I killed the corresponding build threads, then downgraded to version 1.10 of the plugin.
