|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.
What is it that works correct?
Our environment is given up the top of this JIRA,
Expected behaviour is that Jenkins uses some heuristic to detect that a build is "likely stuck.
But when we use this option it just aborts immediately, as shown.
A build can't possibly be stuck after 0 minutes.
We occasionally get builds that are genuinely stuck, we notice this after maybe 3 hours or more.
It would be useful if this feature worked so we could use it to abort those.
If it aborts every build after 0 monutes it's not much use though.