Migrate Scala test setup to a convention plugin

[bric3]

What Does This Do

Replaces the shared Scala test script with the dd-trace-java.conventions.testing.scala convention and migrates its consumers.

Motivation

The name describes Scala test support. Groovy interoperability is configured only when the Groovy plugin is present.

Additional Notes

None.

[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.06 s	13.94 s	[+0.1%; +1.6%] (maybe worse)
startup:insecure-bank:tracing:Agent	12.94 s	12.94 s	[-0.7%; +0.8%] (no difference)
startup:petclinic:appsec:Agent	16.95 s	16.79 s	[-5.5%; +7.5%] (unstable)
startup:petclinic:iast:Agent	17.29 s	17.49 s	[-2.2%; -0.1%] (maybe better)
startup:petclinic:profiling:Agent	17.31 s	17.13 s	[-0.4%; +2.5%] (no difference)
startup:petclinic:sca:Agent	17.33 s	17.27 s	[-0.6%; +1.2%] (no difference)
startup:petclinic:tracing:Agent	16.28 s	16.31 s	[-6.2%; +5.9%] (unstable)

Commit: 617a828d · 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.

[datadog-datadog-us1-prod]

More details

The new convention keeps the prior Scala dependencies and Groovy compile setup. All former script users now use the convention.

Was this helpful? React 👍 or 👎

_{Open Bits AI session}

_{🤖 Datadog Autotest · Commit 617a828 · What is Autotest? · @DataDog review to ask questions · Any feedback? Reach out in #autotest}