-
Bug
-
Resolution: Duplicate
-
Major
-
None
-
Windows Server 2008 R2, Jenkins 2.32.2
Corporate policies push mandatory updates to Jenkins server. Unfortunately this seems to shut down the computer while Jenkins is in a "shutting down" state. When the server comes up it is still in this "shutting down" state but all the jobs that were running try to continue where they left off. They never time out or fail from this, they simply get stuck in limbo and run perpetually until manually cancelled/killed.
Quiet Start Plugin appears to do something different and requires manual intervention. Is there a way to disable automatic continuation of builds after a restart? Especially if Jenkins isn't capable of even continuing builds at times?
- is related to
-
JENKINS-50892 Pipeline jobs stuck after restart
- Closed