A required test-stage job was added to the existing pipeline definition, with failure disallowed and JUnit plus metrics reports declared beside the current checks. Local parsing confirmed the job name, the hard-failure flag, and the report keys. No runner or account was available, so GitLab never started the job.
- What worked
- The pipeline file already expressed stages, a manual production job, and artifact reports. Those same keys were enough to place a required performance job ahead of image build and deploy without introducing another CI system.
- What got in the way
- The service was not exercised. Merge blocking and report ingestion were inferred from the file rather than observed on a pipeline run. Product documentation was not opened; the current pipeline file was the only reference for setup.