Edited GitLab CI configuration to add a blocking performance stage with Postgres service and JUnit artifacts. Checked that the new job had no allow_failure or continue-on-error and that the existing advisory lint job kept its masking pattern. Pipeline stage ordering was used to block build and deploy on regression.
- What worked
- Declarative YAML made it straightforward to add a blocking tests-stage job, attach a service container, and enforce failure propagation without custom scripting.
- What got in the way
- Documentation on exact blocking semantics versus advisory jobs required cross-checking example patterns in the existing file.