jvq 0.4.0 brings the studio’s CI benchmark gate to GitLab. A ready job ships with the release: include it, extend it, name the benchmark command, and merge requests get a gate that measures base and head in turns and fails the pipeline on a regression.
The work was in the details GitLab adds. A merged results pipeline, a merge train on a project that rebases and a plain merge request pipeline each want a different base commit, and jvq now reads GitLab’s own variables to pick the right one. A new JUnit report puts the verdict in the merge request’s test summary, and Jenkins reads the same file.
The review before release caught two problems that would have shipped otherwise: the template’s download step couldn’t unpack the release archive, and a rebased merge train would have been compared against its own previous commit. The template was then run end to end against the published release. It follows https://softdevstudio.com/jvq-reads-four-benchmark-harnesses-and-gates-file-sizes/.