Limit maximum time a build can take
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Linaro Android Infrastructure |
Fix Released
|
Medium
|
Georgy Redkozubov | ||
Bug Description
Recently, I saw cases when builds took ~14hrs to complete (with failure). This happens due to poor scalability of concurrent builds and people not paying attention to already running builds and pumping bunch of them at the same time. Such builds usually hang in repo fetch for hours before being aborted due to git error, EC2 timeouts, or manual action. While improving scalability is hot and important topic, we need some stop-gap measures to deal with the current situation which become.
Proposed solution is to install Build timeout plugin for Jenkins https:/
Related branches
- Paul Sokolovsky: Approve
-
Diff: 26 lines (+22/-0)1 file modifiedutils/mangle-jobs/add-build-timeout.mangle (+22/-0)
| Changed in linaro-android-infrastructure: | |
| importance: | Undecided → High |
| status: | New → Triaged |
| assignee: | nobody → Paul Sokolovsky (pfalcon) |
| Changed in linaro-android-infrastructure: | |
| status: | Triaged → In Progress |
| Paul Sokolovsky (pfalcon) wrote | #1 |
| Changed in linaro-android-infrastructure: | |
| status: | In Progress → Triaged |
| importance: | High → Medium |
| Paul Sokolovsky (pfalcon) wrote | #2 |
| Changed in linaro-android-infrastructure: | |
| importance: | Medium → Low |
| Changed in linaro-android-infrastructure: | |
| importance: | Low → Medium |
| Changed in linaro-android-infrastructure: | |
| assignee: | Paul Sokolovsky (pfalcon) → Georgy Redkozubov (gesha) |
| status: | Triaged → In Progress |
| Changed in linaro-android-infrastructure: | |
| milestone: | none → 2012.02 |
| status: | In Progress → Fix Committed |
| Changed in linaro-android-infrastructure: | |
| status: | Fix Committed → Fix Released |
This actually wasn't started - switch to seeded builds work was made.