- #557 (Failed)
- #558 (Failed)
- #559 (Failed)
- #560 (Failed)
- #561 (Failed)
- #562 (Successful)
- #563 (Successful)
- #564 (Successful)
- #565 (Successful)
- #566 (Successful)
Verifies the integrety of the projects, as builds are executed immediately after a code change was detected. This plan provides no artifiacts (use a nightly build instead).
Recent Plan Failures
| Failed In | Fixed In | Time Taken To Fix | ||
|---|---|---|---|---|
| #556 |
Updated by Tim Jentz
|
#562 |
Manual build by Walter Ebeling
|
6 builds 2 weeks, 2 days, 22 hours, 22 minutes |
| #550 |
Updated by Mircea Carasel
|
#555 |
Updated by Tim Jentz
|
5 builds 6 days, 1 hour, 54 minutes |
- Average time to fix a failure: 1 week, 4 days, 12 hours, 8 minutes
- Average number of builds between fixes: 5.5 builds
- The longest time taken to fix a failure is 2 weeks, 2 days, 22 hours, 22 minutes, from failure starting in build #556.
- The greatest number of builds taken to fix a failure is 6, from failure starting in build #556.