-
Epic
-
Resolution: Won't Do
-
Undefined
-
None
-
None
-
Usability in CI
-
Future Sustainability
-
False
-
-
False
-
Done
-
0% To Do, 0% In Progress, 100% Done
- Jenkins logs:
- Hard to tell where is the failure
We can currently search the logs for exited with code 1 to pinpoint the offending task, and/or search for task names in square brackets (e.g. [BUILD]). We can add more visible text to the logs, or explore the option to send a more elaborate comment report on the MR.
- Hard to tell where is the failure
- Jenkins execution:
- Pipeline doesn't run on Draft MRs
This is possibly configurable via app-interface, at the Jenkins global base-templates config (see gl_pr_check.triggers.gitlab.wip-skip).
- Long time to run, even with failures
Use early-exit + concurrency across verify internal tasks
- Same but at the task level: the unit-test task will always run a long time, even with failures
Use early-exit for Jest
- Pipeline doesn't run on Draft MRs
- is related to
-
OCMUI-2070 [containerized-builds] DRY GitLab/external pipelines
-
- Closed
-