Skip to content

Validate build-time SDK generation with google-java-format - #923

Closed
hectorcast-db wants to merge 1 commit into
mainfrom
validate-format-sync
Closed

hectorcast-db wants to merge 1 commit into
mainfrom
validate-format-sync

Conversation

@hectorcast-db

Copy link
Copy Markdown
Contributor

Draft — not for merge. This validates the Databricks build-time SDK generation against this repo's CI (unit tests) and lets us eyeball the generated + formatted output. It is not a release.

What this is

The SDK surface and the generated test suite are rendered from the OpenAPI spec at build time and formatted in place with google-java-format (run to a fixed point), then synced here. This PR shows the result against main (v0.156.0).

Changes

  • Formatting. The generated surface and the generated test suite are formatted with google-java-format. The generated test files come out byte-identical to their current formatting (0 test-file changes in this diff), confirming the generate-time formatter matches the previous Spotless output.
  • Spotless removed. Dropped from the build (pom.xml, the CI "Check formatting" step, the fmt/fmt-jdk17 Makefile targets, scripts/mvn-spotless-apply.sh). The generator is now authoritative, so a second formatter here would only risk drift.
  • Release/changelog tooling dropped. tagging.py, the tagging and next-changelog workflows, and NEXT_CHANGELOG.md — releases move to the build pipeline.
  • API surface. The remaining source changes are ordinary API evolution since v0.156.0 (apps, catalog, jobs, ml, oauth2, pipelines).

Why

The generated SDK is about to be reviewable per-PR in a diff viewer, so the emitted tree must be cleanly and consistently formatted — including the tests. This PR confirms the formatting is stable and that CI is green without Spotless.

This pull request and its description were written by Isaac.

Draft PR to validate the Databricks Universe build-time SDK generation
against this repo's CI. The SDK surface and the generated test suite are
rendered from the OpenAPI spec at build time and formatted in place with
google-java-format (run to a fixed point), replacing the committed
generated code and the Maven Spotless lint:

- Surface + generated tests formatted by google-java-format; the test
  files come out byte-identical to the current formatting (0 test-file
  changes here), confirming the generate-time formatter matches Spotless's
  output.
- Spotless removed from the build (pom, the CI "Check formatting" step, the
  Makefile targets, scripts/mvn-spotless-apply.sh): the generator is now
  authoritative, so a second formatter here would only risk drift.
- Release/changelog tooling (tagging.py, the tagging and next-changelog
  workflows, NEXT_CHANGELOG.md) is dropped; releases move to the Universe
  pipeline.
- Remaining source changes are ordinary API evolution since v0.156.0.

Not for merge -- this validates formatting and CI only.

Signed-off-by: Hector Castejon Diaz <hector.castejon@databricks.com>
Co-authored-by: Isaac <no-reply@databricks.com>
@hectorcast-db
hectorcast-db deployed to test-trigger-is September 21, 2026 06:56 — with GitHub Actions Active
@hectorcast-db
hectorcast-db deployed to test-trigger-is September 21, 2026 06:56 — with GitHub Actions Active
@github-actions

Copy link
Copy Markdown
Contributor

If integration tests don't run automatically, an authorized user can run them manually by following the instructions below:

Trigger:
go/deco-tests-run/sdk-java

Inputs:

  • PR number: 923
  • Commit SHA: 57bc4907059b4d30ef9973219fc8171bf1122325

Checks will be approved automatically on success.

@hectorcast-db

Copy link
Copy Markdown
Contributor Author

Validation complete — all 18 CI checks passed (fmt, unit-tests matrix ×8, Integration Tests, release dry-run, secrets-access check), confirming the build-time-generated and google-java-format-formatted SDK surface and test suite compile and pass across Java 8/11/17/20 with Spotless removed. This was a throwaway validation branch (not for merge); closing now that the result is captured. The actual change lands via the internal build-time-generation stack.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant