Document one-pipeline source and provenance in AGENTS.md#5515
Merged
Document one-pipeline source and provenance in AGENTS.md#5515
Conversation
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
✅ Tests 🎉 All green!❄️ No new flaky tests detected 🎯 Code Coverage (details) 🔗 Commit SHA: d0e7640 | Docs | Datadog PR Page | Was this helpful? React with 👍/👎 or give us feedback! |
Strech
approved these changes
Mar 27, 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
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 does this PR do?
Adds a "One-Pipeline (GitLab CI)" section to
AGENTS.mddocumenting what theone-pipeline template is, where its source lives, and how it gets distributed
to consuming repos.
Motivation:
Investigating a CI failure in #5486 ("chore(ci) update one-pipeline") took
a long time because there was no documentation explaining where one-pipeline
comes from or how it works. The
package-ocijobs were failing with amisleading error ("42M is greater than 160MB limit") that turned out to be a
local 40MB override in
.gitlab-ci.yml— the template hardcodes the defaultlimit in its error message instead of using the actual variable value.
This section captures the provenance chain so future investigators can go
straight to the source.
Provenance proof (how we know
DataDog/libdatadog-buildis the source):.gitlab/one-pipeline.locked.ymlincludes a remote URL atgitlab-templates.ddbuild.io/libdatadog/one-pipeline/ca/<hash>/one-pipeline.yml.DataDog/libdatadog-buildcontainstemplates/one-pipeline.yml— thesource template with identical structure and content.
libdatadog-build/campaigner-config.ymllists dd-trace-rb as a consumingrepo, with PR title
"chore(ci) update one-pipeline"and branch name"campaigner/update-one-pipeline"— matching exactly how these PRs appear.libdatadog-build/generate_prs.shfetches the content-addressed templateURL from GitLab CI project 2821's
publish-content-addressable-templatesjob artifacts, then uses the campaigner tool to open PRs updating the
locked URL in each consuming repo.
Change log entry
None.
Additional Notes:
None.
How to test the change?
Read the new section in
AGENTS.mdand confirm it matches the provenancechain described above.