Skip to content

Update Spotless to 8.9.0 - #12208

Open
AlexeyKuznetsov-DD wants to merge 1 commit into
masterfrom
alexeyk/update-spotless-8.9.0
Open

Update Spotless to 8.9.0#12208
AlexeyKuznetsov-DD wants to merge 1 commit into
masterfrom
alexeyk/update-spotless-8.9.0

Conversation

@AlexeyKuznetsov-DD

@AlexeyKuznetsov-DD AlexeyKuznetsov-DD commented Aug 13, 2026

Copy link
Copy Markdown
Contributor

What Does This Do

Updates Spotless to 8.9.0 and centralizes its plugin version in the version catalog. GrEclipse remains pinned to 4.27 because of diffplug/spotless#3013.

Motivation

Keep formatter tooling current and use the version catalog consistently.

Additional Notes

Validated with ./gradlew spotlessCheck and the standalone test-published-dependencies Spotless check.

Contributor Checklist

  • Internal build tooling change

@AlexeyKuznetsov-DD AlexeyKuznetsov-DD added tag: ai generated Largely based on code generated by an AI or LLM comp: tooling Build & Tooling type: refactoring tag: no release notes Changes to exclude from release notes tag: dependencies Dependencies related changes labels Aug 13, 2026 — with ChatGPT Codex Connector
@AlexeyKuznetsov-DD AlexeyKuznetsov-DD self-assigned this Aug 13, 2026
@AlexeyKuznetsov-DD
AlexeyKuznetsov-DD marked this pull request as ready for review August 13, 2026 20:10
@AlexeyKuznetsov-DD
AlexeyKuznetsov-DD requested review from a team as code owners August 13, 2026 20:10
@datadog-official

This comment has been minimized.

@dd-octo-sts

dd-octo-sts Bot commented Aug 13, 2026

Copy link
Copy Markdown
Contributor

🟢 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.97 s 14.00 s [-1.0%; +0.5%] (no difference)
startup:insecure-bank:tracing:Agent 12.93 s 12.99 s [-1.3%; +0.5%] (no difference)
startup:petclinic:appsec:Agent 16.89 s 16.75 s [-0.1%; +1.8%] (no difference)
startup:petclinic:iast:Agent 16.90 s 16.45 s [-1.7%; +7.1%] (no difference)
startup:petclinic:profiling:Agent 16.47 s 16.77 s [-2.8%; -0.8%] (maybe better)
startup:petclinic:sca:Agent 16.79 s 16.69 s [-0.5%; +1.7%] (no difference)
startup:petclinic:tracing:Agent 15.68 s 16.08 s [-6.6%; +1.7%] (no difference)

Commit: 9baf1a59 · 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-official datadog-official Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Datadog Autotest: PASS

More details

The centralized Spotless alias resolves from an explicitly imported version catalog in every affected build, and GrEclipse 4.27 remains pinned in both the root predeclaration and shared formatter configuration, preserving the existing formatter dependency contract.

Was this helpful? React 👍 or 👎

Open Bits AI session

🤖 Datadog Autotest · Commit 9baf1a5 · What is Autotest? · @DataDog review to ask questions · Any feedback? Reach out in #autotest

plugins {
java
id("com.diffplug.spotless") version "8.4.0"
alias(libs.plugins.spotless)

@bric3 bric3 Aug 14, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

praise: Thanks, I was eyeing this as well :)

@AlexeyKuznetsov-DD

Copy link
Copy Markdown
Contributor Author

/merge

@gh-worker-devflow-routing-ef8351

gh-worker-devflow-routing-ef8351 Bot commented Aug 14, 2026

Copy link
Copy Markdown

View all feedbacks in Devflow UI.

2026-08-14 14:41:37 UTC ℹ️ Start processing command /merge


2026-08-14 14:41:42 UTC ℹ️ MergeQueue: pull request added to the queue

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


2026-08-14 15:08:31 UTCMergeQueue: The build pipeline contains failing jobs for this merge request

Build pipeline has failing jobs for befe4a1:

⚠️ Do NOT retry failed jobs directly (why?).

What to do next?

  • Investigate the failures and when ready, re-add your pull request to the queue!
  • If your PR checks are green, try to rebase/merge. It might be because the CI run is a bit old.
  • Any question, go check the FAQ.
Details

Since those jobs are not marked as being allowed to fail, the pipeline will most likely fail.
Therefore, and to allow other builds to be processed, this merge request has been rejected and the pipeline got canceled.

@AlexeyKuznetsov-DD

Copy link
Copy Markdown
Contributor Author

/merge

@gh-worker-devflow-routing-ef8351

gh-worker-devflow-routing-ef8351 Bot commented Aug 14, 2026

Copy link
Copy Markdown

View all feedbacks in Devflow UI.

2026-08-14 16:31:36 UTC ℹ️ Start processing command /merge


2026-08-14 16:31:41 UTC ℹ️ MergeQueue: pull request added to the queue

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


2026-08-14 16:42:36 UTCMergeQueue: The build pipeline contains failing jobs for this merge request

Build pipeline has failing jobs for 38a239f:

⚠️ Do NOT retry failed jobs directly (why?).

What to do next?

  • Investigate the failures and when ready, re-add your pull request to the queue!
  • If your PR checks are green, try to rebase/merge. It might be because the CI run is a bit old.
  • Any question, go check the FAQ.
Details

Since those jobs are not marked as being allowed to fail, the pipeline will most likely fail.
Therefore, and to allow other builds to be processed, this merge request has been rejected and the pipeline got canceled.

@AlexeyKuznetsov-DD

Copy link
Copy Markdown
Contributor Author

/merge

@gh-worker-devflow-routing-ef8351

gh-worker-devflow-routing-ef8351 Bot commented Aug 14, 2026

Copy link
Copy Markdown

View all feedbacks in Devflow UI.

2026-08-14 16:53:00 UTC ℹ️ Start processing command /merge


2026-08-14 16:53:04 UTC ℹ️ MergeQueue: pull request added to the queue

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


2026-08-14 17:10:25 UTCMergeQueue: The build pipeline contains failing jobs for this merge request

Build pipeline has failing jobs for 174292f:

⚠️ Do NOT retry failed jobs directly (why?).

What to do next?

  • Investigate the failures and when ready, re-add your pull request to the queue!
  • If your PR checks are green, try to rebase/merge. It might be because the CI run is a bit old.
  • Any question, go check the FAQ.
Details

Since those jobs are not marked as being allowed to fail, the pipeline will most likely fail.
Therefore, and to allow other builds to be processed, this merge request has been rejected and the pipeline got canceled.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

comp: tooling Build & Tooling tag: ai generated Largely based on code generated by an AI or LLM tag: dependencies Dependencies related changes tag: no release notes Changes to exclude from release notes type: refactoring

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants