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 <sternenseemann@systemli.org> Autosubmit: tazjin <tazjin@tvl.su> Tested-by: BuildkiteCI
This commit is contained in:
parent
c4ee942b1c
commit
ee7a724b60
2 changed files with 2 additions and 1 deletions
|
@ -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,
|
||||
|
|
|
@ -114,6 +114,7 @@ depot.nix.readTree.drvTargets {
|
|||
command = buildkiteReportStep {
|
||||
command = [ depot-rust-crates-advisory-report ];
|
||||
style = "warning";
|
||||
context = "depot-crate-advisories";
|
||||
};
|
||||
};
|
||||
};
|
||||
|
|
Loading…
Reference in a new issue