Deduplicate GitLab test job templates - #12199
Conversation
|
🎯 Code Coverage (details) 🔗 Commit SHA: e243804 | Docs | Datadog PR Page | Give us feedback! |
🟢 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. |
There was a problem hiding this comment.
More details
Expanded job behavior preserves AMD64 and ARM64 architecture contracts, including test-agent checks, coverage composition, JVM exclusions, manual feature-branch rules, and the intended artifact-free ARM64 build gate.
📊 Validated against 6 scenarios · Open Bits AI session
🤖 Datadog Autotest · Commit e243804 · What is Autotest? · @DataDog review to ask questions · Any feedback? Reach out in #autotest
What Does This Do
.test_job_commonfor AMD64 and ARM64 jobs.buildjob without downloading its platform-specific artifacts.Motivation
The ARM64 test templates duplicated most of the AMD64 Gradle setup, scripts, report collection, artifacts, retries, and test-agent configuration. That duplication made the architectures prone to drifting whenever shared CI setup changed and made rebases unnecessarily conflict-prone.
Sharing the common template keeps both architectures aligned. The AMD64 build gate also avoids spending ARM64 runner capacity on commits that do not compile.
Additional Notes
git diff --checkpassed; the repository commit hook completed its Gradle/Spotless checks successfully (6,534 tasks).Contributor Checklist
type:and (comp:orinst:) labels in addition to any other useful labelsclose,fix, or any linking keywords when referencing an issueUse
solvesinstead, and assign the PR milestone to the issueJira ticket: N/A