Provides a user interface for order entry
None
Recent failures
| Failed In | Fixed In | Time Taken To Fix | ||
|---|---|---|---|---|
| #184 |
Code changes detected
|
#186 |
Manual run by Mark Goodrich
|
2 builds 18 minutes |
| #134 |
Child of TRUNK-ONEPOINTTENX-350
|
#150 |
Manual run by Darius Jazayeri
|
16 builds 14 weeks, 2 days, 6 hours, 19 minutes |
| #94 |
Child of TRUNK-ONEPOINTTENX-294
|
#95 |
Code changes detected
|
1 build 44 minutes |
| #66 |
Code changes detected
|
#72 |
Code changes detected
|
6 builds 18 hours, 12 minutes |
| #2 |
Manual run by Daniel Kayiwa
|
#4 |
Code changes detected
|
2 builds 20 minutes |
- Average time to fix a failure: 2 weeks, 6 days, 5 hours, 10 minutes
- Average number of builds between fixes: 5.4 builds
- The longest time taken to fix a failure is 14 weeks, 2 days, 6 hours, 19 minutes, from failure starting in build #134.
- The greatest number of builds taken to fix a failure is 16, from failure starting in build #134.