Allow (declarative) pipeline timeout's to mark builds as failed instead of aborted

[bjorn-trollmo]

What feature do you want to see added?

Add an option to the Timeout option to allow setting what status the build should have if it times out.
Currently the timeout option in the Declarative pipeline will not mark a build as failed if it's "triggered", and instead aborts it. This results in the build health (icon) not being affected, and no mail being sent out due to the failure.
This makes it easy to miss builds that fail due to the timeout.
And from what I can tell there is no (easy) way to make the timeout mark a build as failed instead of aborted.

This was changed in the timeout plugin some years back from what I can tell:
https://issues.jenkins.io/browse/JENKINS-9203
https://issues.jenkins.io/browse/JENKINS-9548
And maybe this is relevant?:
https://issues.jenkins.io/browse/JENKINS-55295

Upstream changes

No response

Are you interested in contributing this feature?

No response

[MarkEWaite]

This issue needs to move to the https://github.com/jenkinsci/workflow-basic-steps-plugin/issues repository. The timeout step is provided by the Pipeline: Basic Steps plugin and its issues are tracked in GitHub

[gdhajk]

Could we potentially leverage the timeout step's timeout parameter to include a new option that allows for marking the build as failed when it exceeds the specified duration, similar to how Jenkins handles other build results?

[MarkEWaite]

Could we potentially leverage the timeout step's timeout parameter to include a new option that allows for marking the build as failed when it exceeds the specified duration, similar to how Jenkins handles other build results?

Usually, an optional parameter would be added so that existing Pipelines do not need changes.