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).
None
Recent failures
Failed In | Fixed In | Time Taken To Fix | ||
---|---|---|---|---|
#925 |
Changes by Florian Schmaus <flo@geekplace.eu>
|
Currently failing | ||
#918 |
Changes by Florian Schmaus <flo@geekplace.eu>
|
#924 |
Manual run by daryl herzmann
|
6 builds 1 week, 2 hours, 56 minutes |
#910 |
Changes by Guus der Kinderen and Florian Schmaus <flo@geekplace.eu>
|
#914 |
Manual run by Guus der Kinderen
|
4 builds 1 week, 3 hours, 27 seconds |
#908 |
Changes by Florian Schmaus <flo@geekplace.eu>
|
#909 |
Manual run by daryl herzmann
|
1 build 4 days, 22 hours, 55 minutes |
- Average time to fix a failure: 1 week, 5 days, 1 hour, 39 minutes
- Average number of builds between fixes: 4.75 builds
- The longest time taken to fix a failure is 4 weeks, 1 day, 1 hour, 44 minutes, from failure starting in build #925.
- The greatest number of builds taken to fix a failure is 8, from failure starting in build #925.