Skip to content

feat(spring): Spring Boot 4 — spring-rabbit-1.5 latestDepTest + Boot 4 trie fix#11600

Closed
wconti27 wants to merge 3 commits into
masterfrom
boot4/spring-rabbit-1.5
Closed

feat(spring): Spring Boot 4 — spring-rabbit-1.5 latestDepTest + Boot 4 trie fix#11600
wconti27 wants to merge 3 commits into
masterfrom
boot4/spring-rabbit-1.5

Conversation

@wconti27
Copy link
Copy Markdown
Contributor

@wconti27 wconti27 commented Jun 8, 2026

Summary

Two changes that are strictly required together for Spring Boot 4 latestDepTest support in spring-rabbit-1.5:

1. Muzzle + latestDepTest version bump

  • muzzle.versions: [1.5.0.RELEASE,3)[1.5.0.RELEASE,5) to cover Spring AMQP 3.x + 4.x
  • latestDepTestImplementation spring-boot-starter-amqp: 2.+4.+
  • Added testJvmConstraints { minJavaVersion = JavaVersion.VERSION_17 } (Boot 4 requires Java 17)

2. ByteBuddy ignore trie: Boot 4 class relocation

Spring Boot 4 relocates BackgroundPreinitializer to org.springframework.boot.autoconfigure.preinitialize.BackgroundPreinitializingApplicationListener. The existing trie entry only covered the old class name. Without this fix, the latestDepTest executionError test fails because the class is transformed (loaded into TRANSFORMED_CLASSES_TYPES) but also hits the additional-ignore check.

Added:

0 org.springframework.boot.autoconfigure.preinitialize.BackgroundPreinitializingApplicationListener$*

Verification

./gradlew :dd-java-agent:instrumentation:spring:spring-rabbit-1.5:latestDepTest -PtestJvm=17BUILD SUCCESSFUL with Spring Boot 4.0.0-RC2.

Part of: #11597

🤖 Generated with Claude Code

@wconti27 wconti27 requested review from a team as code owners June 8, 2026 16:23
@wconti27 wconti27 requested review from PerfectSlayer and jordan-wong and removed request for a team June 8, 2026 16:23
@dd-octo-sts
Copy link
Copy Markdown
Contributor

dd-octo-sts Bot commented Jun 8, 2026

Hi! 👋 Thanks for your pull request! 🎉

To help us review it, please make sure to:

  • Add at least one type, and one component or instrumentation label to the pull request

If you need help, please check our contributing guidelines.

@dd-octo-sts
Copy link
Copy Markdown
Contributor

dd-octo-sts Bot commented Jun 8, 2026

PR Blocked - Invalid Label

The pull request introduced unexpected labels:

  • ai-generated

This PR is blocked until:

  1. The invalid labels are deleted, and
  2. A maintainer deletes this comment to unblock the PR

Note: Simply removing labels from the pull request is not enough - a maintainer must delete this comment then remove the label to remove the block.

@datadog-datadog-prod-us1
Copy link
Copy Markdown
Contributor

Pipelines

Fix all issues with BitsAI

⚠️ Warnings

🚦 2 Pipeline jobs failed

Check pull requests | Check pull requests   View in Datadog   GitHub Actions

Validate PR Label Format | Check pull request labels   View in Datadog   GitHub Actions

Useful? React with 👍 / 👎

This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 420134b | Docs | Datadog PR Page | Give us feedback!

@wconti27 wconti27 marked this pull request as draft June 8, 2026 16:25
Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 420134bb10

ℹ️ 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".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

}
}

testJvmConstraints {
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Move testJvmConstraints after applying the Java plugin

The testJvmConstraints extension is registered by the dd-trace-java.test-jvm-constraints plugin applied from gradle/java.gradle/java_no_deps.gradle, but this block runs before this script applies java.gradle below. When Gradle evaluates this instrumentation project, the testJvmConstraints { ... } call is an unknown method and configuration fails before latestDepTest can run; move the block after the apply from line or configure the latestDepTest task after the suite is created.

Useful? React with 👍 / 👎.

@PerfectSlayer
Copy link
Copy Markdown
Contributor

Please stop creating label, re-use the existing one instead.

@dd-octo-sts
Copy link
Copy Markdown
Contributor

dd-octo-sts Bot commented Jun 8, 2026

🟢 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 13.92 s 13.88 s [-0.7%; +1.3%] (no difference)
startup:insecure-bank:tracing:Agent 12.85 s 12.99 s [-2.3%; +0.1%] (no difference)
startup:petclinic:appsec:Agent 16.97 s 16.81 s [-0.4%; +2.2%] (no difference)
startup:petclinic:iast:Agent 16.86 s 16.96 s [-1.7%; +0.5%] (no difference)
startup:petclinic:profiling:Agent 16.90 s 17.02 s [-2.5%; +1.1%] (no difference)
startup:petclinic:sca:Agent 16.79 s 16.59 s [-0.3%; +2.7%] (no difference)
startup:petclinic:tracing:Agent 16.30 s 16.02 s [+0.2%; +3.3%] (maybe worse)

Commit: 420134bb · 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.

@wconti27 wconti27 closed this Jun 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants