From bb6ecc6b64e2281beddece879a7182b3c7f60718 Mon Sep 17 00:00:00 2001 From: Gabor Gevay Date: Sun, 6 Sep 2026 11:37:14 +0200 Subject: [PATCH] ci: label the staging spec-sheet step by what it runs The two production steps read " (against )", while the staging step said only where it runs. It runs the envd QPS and envd objects scalability groups and the cluster object limits group, so its label now follows the same pattern, with "object count" spelled out so the limit is not mistaken for a size limit. The "Cluster spec sheet" prefix stays, which is what the mzcompose plugin's services.log check matches on. Co-Authored-By: Claude Fable 5.1 --- ci/spec-sheet/pipeline.template.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ci/spec-sheet/pipeline.template.yml b/ci/spec-sheet/pipeline.template.yml index a9dac5052a1c4..0550b40081816 100644 --- a/ci/spec-sheet/pipeline.template.yml +++ b/ci/spec-sheet/pipeline.template.yml @@ -111,7 +111,7 @@ steps: queue: linux-aarch64-small - id: cluster-spec-sheet-staging - label: "Cluster spec sheet: Staging" + label: "Cluster spec sheet: envd Scalability + Cluster Object Count Limits (against Staging)" timeout_in_minutes: 3600 depends_on: devel-docker-tags parallelism: 7