You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I have a plan that includes a single stage with mutliple jobs each with unique requirements. I would like builds for these jobs to be considered "hung" and terminated if they've been queued for over 3 hours, since it is not uncommon for some requirements to be unable to be met.
The "Override default hanging build detection criteria" option is selected for all jobs, and the "Build time multiplier" is set to 2.5, the "Log quiet time" parameter is set to 5 (minutes), and the "Build queue timeout" is set to 180 (minutes).
However, I am still observing behavior where a couple of the jobs remain queued for over 10 hours because there is no agent capable of building them (basically until I manually cancel the build). Shouldn't the 3-hour "Build queue timeout" have kicked in and caused this build to be considered "hung" and therefore killed? Or am I misunderstanding how these parameters and hung builds work?
I'm using Bamboo Server 6.10.6.