PB-899 Add --scope flag to buildkite-agent annotate command
#3569
+28
−3
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
We're currently building a feature where agents (and the jobs running on them) will be able to decide the "scope" for an annotation — ie, whether it's an annotation on the build (the current status quo), or an annotation on a particular job (new and shiny!).
This PR adds a flag to the agent to let callers decide the scope for their annotation. They can use
--scope build(or omit the flag entirely) to scope to a build, or use--scope jobto display their annotation on a job.Context
PB-899
Testing
go test ./...). Buildkite employees may check this if the pipeline has run automatically.go fmt ./...)Disclosures / Credits
It's all me, baby.