[SDCT-814] Add ci.pipeline.display_name tag for Buildkite - #110
Merged
Conversation
BUILDKITE_PIPELINE_SLUG was being used for ci.pipeline.name, which is a slug, not the human-readable pipeline name. We can't change ci.pipeline.name's source since the backend fingerprints pipelines by its current value, so instead add a new, additive ci.pipeline.display_name tag sourced from BUILDKITE_PIPELINE_NAME. Mirrors the identical fix already shipped in dd-trace-js, dd-trace-py, dd-trace-java, dd-trace-dotnet, dd-trace-go, datadog-ci-rb, dd-sdk-swift-testing, and datadog-ci.
![datadog-official[bot]](https://avatars.githubusercontent.com/in/1358509?s=60&v=4){kind=small}
There was a problem hiding this comment.
More details
The new Buildkite display-name tag is additive and preserves the existing slug used by pipeline identity. Adversarial execution confirmed normal, whitespace-heavy, missing, and empty environment values behave correctly; no production-user regression was identified.
📊 Validated against 4 scenarios · Open Bits AI session
🤖 Datadog Autotest · Commit 687c8a5 · What is Autotest? · @DataDog review to ask questions · Any feedback? Reach out in #autotest
anmarchenko
approved these changes
Jul 28, 2026
anmarchenko
approved these changes
Jul 28, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
What
Adds a new, additive
ci.pipeline.display_nametag for Buildkite, sourced fromBUILDKITE_PIPELINE_NAME(the real pipeline name), alongside the existingci.pipeline.nametag.Why
ci.pipeline.namecurrently carries the Buildkite pipeline slug (BUILDKITE_PIPELINE_SLUG), not the real pipeline name. We can't changeci.pipeline.name's value without a breaking change, since the backend computes pipeline fingerprinting from it today. This PR adds the real name as a new, separate tag instead. A future major-version release will eventually swapci.pipeline.nameover to the real name and retire this tag — that's out of scope here.Scope is intentionally limited to Buildkite only; no other CI provider is touched, and
ci.pipeline.name's source is untouched.