Migrate Kotlin test setup to a convention plugin - #12284
Migrate Kotlin test setup to a convention plugin#12284gh-worker-dd-mergequeue-cf854d[bot] merged 2 commits into
Conversation
Keep shared Kotlin and default Groovy test wiring behind plugin callbacks.
Cover JVM test suites and test fixtures through Gradle source-set APIs.
This comment has been minimized.
This comment has been minimized.
🟢 Java Benchmark SLOs — All performance SLOs passed
PR vs. master results
Commit: Load and DaCapo benchmarks can be triggered manually in the GitLab pipeline. Results will appear in the Benchmarking Platform UI after completion. |
68b3d69 to
f6879b1
Compare
There was a problem hiding this comment.
More details
The convention keeps the prior Kotlin and Groovy classpath wiring. It also applies this wiring to JVM test suites and test fixtures.
🤖 Datadog Autotest · Commit f6879b1 · What is Autotest? · @DataDog review to ask questions · Any feedback? Reach out in #autotest
f6879b1 to
a8b24c4
Compare
|
/merge |
|
View all feedbacks in Devflow UI.
The expected merge time in
|
What Does This Do
Replaces the shared Kotlin test script with the
dd-trace-java.conventions.testing.kotlinconvention and migrates its four consumers. The convention also wires Kotlin outputs for JVM test suites and test fixtures.Motivation
The name describes Kotlin test support. Groovy interoperability is configured only when the Groovy plugin is present and follows Gradle test source sets.
Additional Notes
This convention lands in the preferred
build-logic/location because projects apply it directly, on demand. It could move tobuildSrc/, but that is not the desired goal. Conventions should move there only when their types or plugins must be visible to otherbuildSrc/plugins or legacy script plugins through Gradle’s shared build-script classloader.