| I guess there are (at least) two different problems: (1) the Docker container presumably is terminated and (2) loading the build state fails because de-serialization does not work or is maybe intentionally not supported because of issue #1? Sam Van Oort Just a naive thought, but do you think there is a workaround possibility related/similar to your recently introduced "pipeline speed/durability level" code: basically another durability level that only considers finished stages (i.e. persists only after finishing a stage); ideally linked with "Manage Jenkins > Prepare for Shutdown" (= http://<jenkins-server>/quietDown) action to not just waiting for the finishing of the currently running step, but only to stop at the end of the current stage to allow a gentle shutdown possibility (in between stages, once the build state was persisted. Actually:
- the documentation for "Manage Jenkins > Prepare for Shutdown" (= http://<jenkins-server>/quietDown) action is not really correct, as it says to "stops executing new builds" although it seems to pause
 running pipelines after the completion of the currently running pipeline step
- after cancelling the shutdown (cancelQuietDown) I then have to pause + resume the running pipeline (to kind of wake it up?) that was in the middle of a sleep step, when I triggered "Manage Jenkins > Prepare for Shutdown"!?
I am not sure if my imagined use case is rather theoretical or irrelevant: in case I have many pipelines AND they are longer running I may have great difficulties to find a time slot for e.g. installing Jenkins plug-in updates including restarting the Jenkins master subsequently? (Thus I am now ignoring e.g. pipeline resumability because of "unplanned Jenkins outages" like crashes or network connection problems. I think.) |
