-
Bug
-
Resolution: Not A Defect
-
Major
-
None
Current setup is OSX for both master and slave. Slave is mavericks, master is mountain lion.
I have a build job that executes a single git command to clone a repository. Some repositories are very large and take many hours to clone. However, the absolute build timeout is set to 90 minutes, and so should stop the build. If I am understanding correctly, absolute should kill the build regardless of whether there's activity or not.
Attached is a threaddump from master. I think I can reproduce if you need more information. Stopping the process from jenkins UI works as expected.
[JENKINS-23018] Absolute build timeout doesn't stop the build
Yossarian King
added a comment - In case anyone else stumbles across this while trying to get build timeouts to work ...
1. Simply turning on "Abort the build if it's stuck" is not enough. You also need to add a Timeout Action to Abort the build.
2. The minimum build timeout is 3 minutes, even if you put 1 as the configuration setting.
Now that I know this, my timeouts are working great. But before I knew #1 I couldn't understand why my timeout wasn't working, and then when I created a dummy project to sleep for two minutes and timeout after one minute, #2 tripped me up.
IMHO both of these are confusing – I think "Abort the build" should be the default action if none is specified, and you should be able to set any timeout limit you want (preferably in seconds, not minutes).
Yossarian King
added a comment - In case anyone else stumbles across this while trying to get build timeouts to work ...
1. Simply turning on "Abort the build if it's stuck" is not enough. You also need to add a Timeout Action to Abort the build.
2. The minimum build timeout is 3 minutes, even if you put 1 as the configuration setting.
Now that I know this, my timeouts are working great. But before I knew #1 I couldn't understand why my timeout wasn't working, and then when I created a dummy project to sleep for two minutes and timeout after one minute, #2 tripped me up.
IMHO both of these are confusing – I think "Abort the build" should be the default action if none is specified, and you should be able to set any timeout limit you want (preferably in seconds, not minutes). 
ikedam
added a comment - - edited The first one is reported in JENKINS-23740 , and should be fixed in the next release. 
Build-timeout plugin starts its timer AFTER scm phase.
And so it never catches timeout of SCM.