Do not allow failure for separate e2e test jobs
What does this MR do and why?
Setup for not allowing to fail for main trigger job was introduced due to need to validate trigger-omnibus
job which was part of package-and-test
pipeline. This introduced a few issues:
- Failed tests became invisible outside of child pipelines (there is still
❌ on a trigger job when jobs inside of it fail even when trigger job itself is allowed to fail) - We had to introduce additional mechanisms for slack notifications to work as it relied on jobs failing.
This seems to be not the case anymore mainly because trigger-omnibus
job has been extracted outside of package-and-test
pipeline, so we probably can revert back to old simpler setup.
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.