Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: databricks/databricks-sdk-java
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: main
Choose a base ref
...
head repository: databricks/databricks-sdk-java
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: debug/jfrog-prelease-repro
Choose a head ref
Checking mergeability… Don’t worry, you can still create the pull request.
  • 2 commits
  • 1 file changed
  • 1 contributor

Commits on Apr 23, 2026

  1. Add debug workflow to reproduce -Prelease failure against JFrog mirror 

    Scoped to the debug/jfrog-prelease-repro branch. Runs `mvn -Prelease` with
the same JFrog OIDC + mirror setup as the release workflow so we can share
a clean reproduction with JFrog support. No publish/upload/release side
effects (no GPG signing, no artifact upload, no deploy).

Co-authored-by: Isaac
    @hectorcast-db
    hectorcast-db committed Apr 23, 2026
    Configuration menu
    Copy the full SHA
    5d5519a View commit details
    Browse the repository at this point in the history

  2. Bust Maven cache in debug workflow 

    Previous run restored a cached ~/.m2/repository, so central-publishing-maven-plugin was served from cache and the build got past startup (failing later at gpg:sign, masked). Without a cache, Maven is forced to resolve -Prelease plugins through the JFrog mirror fresh each run, which is the exact failure mode we want to show JFrog.

Co-authored-by: Isaac
    @hectorcast-db
    hectorcast-db committed Apr 23, 2026
    Configuration menu
    Copy the full SHA
    7e6253e View commit details
    Browse the repository at this point in the history
Loading