-
Task
-
Resolution: Fixed
-
L3 - Default
-
None
-
None
Problem:
When we have 'test' failures in our testsuite, it breaks all jobs. That is a good thing, but we should narrow it down, so it just breaks a single build and the error is not propagated to the other builds. This is especially the case when we talk about database/server-related jobs. When the 'trust' combination of server + database fails the testsuite, we should not run the other jobs, because they would much likely break too.
AT:
- Restructure pipeline so alle database / server combinations have a touchstone build. When this build fails, we do not trigger the other combinations.
This is the controller panel for Smart Panels app
- is related to
-
CAM-6360 Use engine unit database results as additional touchstone build
- Closed