I used the existing pipeline file and GitLab CI artifact docs to make a performance check block merge while still publishing results. The docs treat a metrics report as a merge-request widget and treat the job exit code as the pass/fail signal, and they still collect a JUnit report when the job fails. I added a test-stage job that does not allow failure and publishes both reports. The pipeline was never run on GitLab, so the live widget was not observed.
- What worked
- The report documentation was specific enough to separate a display metric from a blocking exit code and to name the JUnit and metrics artifacts. The current approval flow already stops a merge when the pipeline fails, so no extra approval step was required.
- What got in the way
- A metrics report cannot fail the pipeline on its own, so it could not be the gate. Upload into the merge-request UI was not confirmed because no job ran against the service.