-
Suggestion
-
Resolution: Fixed
-
None
-
None
The hung build detection scheme uses both elapsed build time and time-since-log-update to trigger hung-build detection. It appears that for the 1st build on a branch plan, there is no average build time and hence no ability to detect hung builds.
We observed a failure to detect a hung build when the build did not update the log for over two days. (The average time for this build on other plan branches was ~6 minutes. The build hang time multiplier was set to 10x and the log timeout was 150 minutes).
I would suggest that for the 1st build on a branch:
A) Ignore the detection based on average build time and use log-update time only, or
B) Use the average build time from a different branch plan (or the average build time of all branch plans)
- relates to
-
BAM-931 provide a maximum time limit for builds; if it exceeds, kill the build and fail it
- Closed
[BAM-17921] Build hang detection does not work on new branches
Workflow | Original: JAC Suggestion Workflow [ 3015720 ] | New: JAC Suggestion Workflow 3 [ 3601957 ] |
Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: Confluence Workflow - Public Facing v4 [ 2703135 ] | New: JAC Suggestion Workflow [ 3015720 ] |
Issue Type | Original: Improvement [ 4 ] | New: Suggestion [ 10000 ] |
Workflow | Original: Bamboo Workflow 2016 v1 [ 1608377 ] | New: Confluence Workflow - Public Facing v4 [ 2703135 ] |
Fix Version/s | New: 6.3.0 [ 74985 ] | |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Needs Triage [ 10030 ] | New: Resolved [ 5 ] |