[PerfectSlayer]

What Does This Do

Makes TracerVersionPlugin build a release version only in the GitLab pipeline of that tag.

• In GitLab (GITLAB_CI set), a build checked out on a tag vX.Y.Z keeps the version X.Y.Z only when CI_COMMIT_TAG is vX.Y.Z.
• Any other GitLab pipeline on the tagged commit, such as master or a release/v* branch, builds the next snapshot version, as if there were later commits. For example, master builds X.(Y+1).0-SNAPSHOT and release/vX.Y.x builds X.Y.(Z+1)-SNAPSHOT.
• Builds outside GitLab (local builds, GitHub Actions) are unchanged.

Motivation

The v1.68.0 release ended up with two Maven Central deployments. Both pipelines ran on the tagged commit 36cefc7:

• Master pipeline 147390587: its build job ran before the tag was visible and built 1.68.0-SNAPSHOT. Its deploy_to_maven_central job started at 08:22 UTC, re-resolved the version through git describe, got the exact tag, and computed 1.68.0. publishToSonatype closeSonatypeStagingRepository then created deployment changing List<Span> for List<DDSpan> #1.
• Tag pipeline 147390895 created deployment First PR - Implements the Opentracing API #2 at 08:42 UTC.

The version only depended on git describe, so any job checking out the tagged commit after the tag push built the release version, whatever pipeline it belonged to.

Additional Notes

• Tests: assertTracerVersion now always removes GITLAB_CI and CI_COMMIT_TAG from the inherited environment, so the tests don't depend on the GitLab pipeline running them. There are new cases for a master pipeline, a release branch pipeline, and another tag's pipeline on a tagged commit. Run them with ./gradlew :buildSrc:test -PrunBuildSrcTests --tests 'datadog.gradle.plugin.version.*'.
• When the version is forced to a snapshot on an exact tag, -SNAPSHOT is appended even with useSnapshot = false, so the option can't produce a release-looking version. Nothing sets that option today.

Contributor Checklist

• Format the title according to the contribution guidelines
• Assign the type: and (comp: or inst:) labels in addition to any other useful labels
• Avoid using close, fix, or any linking keywords when referencing an issue
  Use solves instead, and assign the PR milestone to the issue
• Update the CODEOWNERS file on source file addition, migration, or deletion
• Update public documentation with any new configuration flags or behaviors
• Once approved, use merge queue to merge the PR

Jira ticket: APMLP-1743

🤖 Generated with Claude Code

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-27T07:07:06.070025Z	4ac5148	Draft marked ready
🔒 Security Review	✅ Completed 2026-10-27T07:08:09.198548Z	4ac5148	Draft marked ready

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[datadog-datadog-prod-us1-2]

More details

The matching-tag check prevents GitLab branch pipelines on tagged commits from producing release versions while preserving behavior outside GitLab. The completed static review found no actionable regression, and no human PR discussion was present.

Was this helpful? React 👍 or 👎

_{Open Bits AI session}

_{🤖 Bits Code Review · Commit 4ac5148}

[datadog-datadog-prod-us1-2]

🎯 Code Coverage (details)
• Patch Coverage: 100.00%
• Overall Coverage: 59.45% (+0.01%)

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 70668c7 | Docs | Give us feedback!}

[dd-octo-sts]

🟢 Java Benchmark SLOs — All performance SLOs passed

Suite	Status
Startup	🟢 pass

SLO thresholds are defined here based on automatically generated metrics. A warning is raised when results are within 5% of the threshold.

PR vs. master results

Scenario	Candidate	master	Δ (95% CI of mean)
startup:insecure-bank:iast:Agent	14.01 s	13.92 s	[-0.0%; +1.4%] (no difference)
startup:insecure-bank:tracing:Agent	12.88 s	12.99 s	[-1.5%; -0.2%] (maybe better)
startup:petclinic:appsec:Agent	17.03 s	16.99 s	[-0.6%; +1.0%] (no difference)
startup:petclinic:iast:Agent	16.94 s	16.92 s	[-0.7%; +0.9%] (no difference)
startup:petclinic:profiling:Agent	16.61 s	16.16 s	[-1.5%; +7.1%] (no difference)
startup:petclinic:sca:Agent	17.04 s	17.06 s	[-0.9%; +0.7%] (no difference)
startup:petclinic:tracing:Agent	16.16 s	16.16 s	[-0.9%; +0.9%] (no difference)

Commit: 70668c79 · CI Pipeline · Benchmarking Platform UI

---

Load and DaCapo benchmarks can be triggered manually in the GitLab pipeline. Results will appear in the Benchmarking Platform UI after completion.

[bric3]

The intent and fix is sound, but I'd avoid the lambda indirections.

[PerfectSlayer]

/merge

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-10-27 13:47:46 UTC ℹ️ Start processing command /merge

---

2026-10-27 13:47:50 UTC ℹ️ MergeQueue: pull request added to the queue

The expected merge time in master is approximately 1h (p90).

---

2026-10-27 15:16:31 UTC ℹ️ MergeQueue: This merge request was merged