Add default scala template to databricks cli #3906
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
garlandz-db
requested review from
andrewnester,
anton-107,
denik,
lennartkats-db,
pietern and
shreyas-goenka
as code owners
lennartkats-db
requested changes
Nov 11, 2025
Contributor
lennartkats-db
left a comment
lennartkats-db
left a comment
There was a problem hiding this comment.
Great!!! Please tell your coding agent to add it to the list of templates and to add acceptance tests for it!
garlandz-db
force-pushed
the
default_scala_template
branch
from
9b72220 to
1611523
Compare
Contributor
|
Please also add an entry in You can look at earlier entries in |
garlandz-db
force-pushed
the
default_scala_template
branch
from
1ff61ca to
e4473a8
Compare
NEXT_CHANGELOG.md
Outdated
| ### Dependency updates | ||
|
|
||
| ### Bundles | ||
| * Add `default-scala` template for Scala projects to build jar jobs in Serverless or with Standard Clusters ([#XXXX](https://github.com/databricks/cli/pull/XXXX)) |
Contributor
There was a problem hiding this comment.
Please update the URL inline
Contributor
lennartkats-db
left a comment
lennartkats-db
left a comment
There was a problem hiding this comment.
Please take a look at the test failures + the NEXT_CHANGELOG file. I just merged the associated databricks/bundle-examples#119 PR.
And please let me know if you made any changes compared to the original template in the samples repo.
garlandz-db
force-pushed
the
default_scala_template
branch
2 times, most recently
from
dbb4781 to
be1d47a
Compare
garlandz-db
force-pushed
the
default_scala_template
branch
from
be1d47a to
90b795d
Compare
Contributor
Author
|
the changes made under default-scala were all whitespaces and formatting. claude's summary |
lennartkats-db
approved these changes
Nov 13, 2025
|
An authorized user can trigger integration tests manually by following the instructions below: Trigger: Inputs:
Checks will be approved automatically on success. |
Collaborator
10 failing tests:
Top 50 slowest tests (at least 2 minutes):
|
deco-sdk-tagging bot
added a commit
that referenced
this pull request
Nov 19, 2025
## Release v0.278.0 ### Dependency updates * Upgrade Go SDK to 0.91.0 ([#3948](#3948)) * Bump Alpine Linux to 3.22 in the Docker image ([#3942](#3942)) ### Bundles * Update templates to use serverless environment version 4 and matching Python version ([#3897](#3897)) * Add a language prompt to the `default-minimal` template ([#3918](#3918)) * Add `default-scala` template for Scala projects with SBT build configuration and example code ([#3906](#3906))
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes
This adds a new default scala DABs template as a follow up to databricks/bundle-examples#119
Why
This is to provide an off the shelf template for customers to start using scala dbconnect to develop scala jobs in Databricks
Tests
Manually tested user flow interactively and as job workload for both standard and serverless