We've seen some multi-threaded code tests fail by just hanging sometimes on some platforms. The CI tool will then just block forever. Having some sensible maximum time would rock
- is duplicated by
-
BAM-2848 Time out builds if they are taking too long
- Closed
-
- Closed
-
- Closed
- is related to
-
- Closed
-
- Closed
-
- Closed
- relates to
-
- Closed
- mentioned in
-
Page Loading...
-
-
-
-
-
-
[BAM-931] provide a maximum time limit for builds; if it exceeds, kill the build and fail it
Hung Build Killer plugin functionality was bundled into Bamboo 6.4 with configuration UI improvements. See Bamboo 6.4 release notes for details
If this is not going to be built into Bamboo, would it be possible to have an officially supported version/variant of the HungBuildKiller plugin? We upgraded to 6.0 recently and the HungBuildKiller isn't available again.
Guys, FWIW
take a look at this plugin: https://marketplace.atlassian.com/plugins/com.atlassian.buildeng.hung-build-killer/server/overview
I don't think this one is on Atlassian's priority list at all. I made my previous comment on this issue around 3 years ago and obvious they have no intension for a fix.
Ron Edgecomb II
added a comment - We really need to see this feature implemented, it's critical as we have hundreds of build plans.
This ticket has been around for quite some time, it would be nice to have an update on the status/intent 😐
Ron Edgecomb II
added a comment - We really need to see this feature implemented, it's critical as we have hundreds of build plans.
This ticket has been around for quite some time, it would be nice to have an update on the status/intent 😐 This is a big problem for us that makes Bamboo CI not a very good fit despite all the great integration with other Atlassian tools.
Guys, please implement this feature as it would be a life saver.
Imagine build setups with hundreds of build plans - it's impossible to handle hung builds manually.
Sylvain Lamontagne
added a comment - Any news on when we could expect an automatic failure and killing of an Hung job ?
It is a feature that would really be useful for us, as one of our build agent is block and can't build anything else when a Job is hung.
Sylvain Lamontagne
added a comment - Any news on when we could expect an automatic failure and killing of an Hung job ?
It is a feature that would really be useful for us, as one of our build agent is block and can't build anything else when a Job is hung. 
Vincent Thibault
added a comment - This feature would save us a lot of delays. We often get hung jobs in our overnight builds. Those build agents cannot take on anymore builds in the queue. People are unhappy the next morning. 2 of our overnight builds take a little more that 5-7 hours in duration. In our most recent release branch 2 of our overnight builds are now taking 4-5 hours in duration (we're improving our build duration, but are still far from quick turnaround). But still, loosing a night has a major negative effect on our development teams.
Vincent Thibault
added a comment - This feature would save us a lot of delays. We often get hung jobs in our overnight builds. Those build agents cannot take on anymore builds in the queue. People are unhappy the next morning. 2 of our overnight builds take a little more that 5-7 hours in duration. In our most recent release branch 2 of our overnight builds are now taking 4-5 hours in duration (we're improving our build duration, but are still far from quick turnaround). But still, loosing a night has a major negative effect on our development teams. Are we able to have the current HungBuildKiller plugin source code made visible in order to fix bugs in it on our own?
is there an API to support this? Where I can script this in and hit the API to kill the hung-up builds?