-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
Jenkins 2.73.3 on Linux (Centos 7).
All plugins up to date.
Declarative pipeline runs through its stages. User clicks abort/cancel red button, pipeline drops into post step as expected. Post has an always block. User then clicks abort again (they are impatient), post is executing always, most likely sh commands, and is then terminated. The 2nd abort should be ignored and the post always should be allowed to complete? There is only one block in the post (always). Post always should be allowed to do cleanup (or is there away to turn off the abort signal once it enters the post always?).
A bit of googling shows there is a soft kill versus a hard kill. So ideally clicking the red box would generate a soft kill, while a hard kill can be done via listing the console output and clicking on `Click here to forcibly terminate running steps`? If anyone has any tips or things I can try out, please let me know.
If you wish to reproduce, here is a sample pipeline: