I edit a job configuration and check (select) either the "Fail the build" or "Writing the build description" options, and click save.
If I go back and look at the configuration, my changes were not saved.
This problem occurs in build-timeout 1.10.
Fail the build is only available if you select the "Likely stuck".
The UI is a little bit confusing.
It is fixen in the HEAD.
It is fixed in the HEAD.
Hm right. Same here.
It seems it's fixed in git, just not released.
How do we prompt the plugin maintainer to release?
I saw here http://jenkins.361315.n4.nabble.com/JIRA-JENKINS-14158-Change-to-build-timeout-job-configuration-not-saved-td4632182.html that "Fail the build is only available if you select the Likely stuck".
In the current version of the plugin, you can select "Fail the build" indeed only on the "Likely stuck" option.
This annoying - I'd like to mark my builds as failed after an absolute timeout...
I would also like to mark the build as failed after an absolute timeout.
We also have been holding back on version 1.9 (one one of our servers) of this plug in since it properly fails the build after an absolute timer timeout.
What's not clear from the discussion here is if the fix in the repo both fixes the configuration saving issue but also fixes the confusing/inappropriate placement of the "fail the build" checkbox only under the "Likely stuck" option.
The following pull request will fix.
I'll merge it and release as 1.11.
fixed in 1.11