Publishes the frontend spa-assembly-config.json to Maven (separate plan, so this can be run in parallel with the deploy step)
None
Recent plan failures
| Failed In | Fixed In | Time Taken To Fix | ||
|---|---|---|---|---|
| #355 |
Child of O3-BF-361
|
#360 |
Child of O3-BF-366
|
5 builds 15 hours, 55 minutes |
| #353 |
Child of O3-BF-359
|
#354 |
Child of O3-BF-360
|
1 build 39 minutes |
| #350 |
Child of O3-BF-356
|
#351 |
Child of O3-BF-357
|
1 build 7 minutes |
| #347 |
Child of O3-BF-353
|
#349 |
Child of O3-BF-355
|
2 builds 18 minutes |
| #344 |
Child of O3-BF-350
|
#345 |
Child of O3-BF-351
|
1 build 1 hour, 1 minute |
| #341 |
Child of O3-BF-347
|
#342 |
Child of O3-BF-348
|
1 build 39 minutes |
| #173 |
Child of O3-BF-178
|
#264 |
Child of O3-BF-269
|
91 builds 1 week, 4 days, 22 hours, 25 minutes |
- Average time to fix a failure: 1 day, 19 hours, 35 minutes
- Average number of builds between fixes: 14.57 builds
- The longest time taken to fix a failure is 1 week, 4 days, 22 hours, 25 minutes, from failure starting in build #173.
- The greatest number of builds taken to fix a failure is 91, from failure starting in build #173.