-
Improvement
-
Resolution: Unresolved
-
Minor
-
None
The attached screenshot is from ci.jenkins.io. I haven't understood this user experience for some time, but today it's especially frustrating.
I think Pipeline could be improved if instead of showing links which an administrator must click ("It appears you're trying to abort a Pipeline, could I help you with that?") the Pipeline should just abort the Pipeline.
In the screenshot, I must click three times to accomplish the behavior I originally intended when I aborted the Pipeline in the first place. Instead, the forcible termination of running steps, and t hen forcible killing of the entire Pipeline should happen automatically after some timeout.
I've thought about this sucker before. There is logic behind the idea of the initial abort just killing the current step, so that other non-failfast parallels would continue, or Declarative post actions can still run, etc. But leaving things dangling forever if killing the single step doesn't work is a bad experience. I'd say we should do something like the following when you click abort:
I just don't see any reason for requiring human intervention in those cases.