From ee7a724b608fa30e3664bbc2e99e19e72559b15a Mon Sep 17 00:00:00 2001 From: Vincent Ambo Date: Mon, 26 Dec 2022 13:16:10 +0300 Subject: fix(ops/pipelines): explicitly set contexts for annotations I think what might be going on with b/231 is that the annotations somehow started conflicting because they don't have contexts set. Lets try setting a context and see if it changs anything ... Change-Id: I62ed57f9e24f08e4e7215f05d35cfa769e2e2c24 Reviewed-on: https://cl.tvl.fyi/c/depot/+/7640 Reviewed-by: sterni Autosubmit: tazjin Tested-by: BuildkiteCI --- ops/pipelines/static-pipeline.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'ops/pipelines') diff --git a/ops/pipelines/static-pipeline.yaml b/ops/pipelines/static-pipeline.yaml index 8fcf240f74..c3d791f641 100644 --- a/ops/pipelines/static-pipeline.yaml +++ b/ops/pipelines/static-pipeline.yaml @@ -41,7 +41,7 @@ steps: if test -n "$${GERRIT_CHANGE_URL-}"; then echo "This is a build of [cl/$$GERRIT_CHANGE_ID]($$GERRIT_CHANGE_URL) (at patchset #$$GERRIT_PATCHSET)" | \ - buildkite-agent annotate + buildkite-agent annotate --context cl-annotation fi # Attempt to fetch a target map from a parent commit on canon, -- cgit 1.4.1