- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-05-2026 10:29 PM
Eventually, I would like to be able to upload the wheel to a dynamic location based on its git_commit and then use any past version of the wheel in my job - but for right now I am just trying to get this simple example to work.
I know I can make this work using the libraries tag when using a traditional job cluster - but how do I get this to work for serverless?
I haven't found an example of this workflow on the forums so far - the closest I saw was someone using notebooks but notebook tasks that consume a wheel aren't the same thing as a wheel task.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-12-2026 08:43 PM - edited 02-12-2026 09:02 PM
For a Python wheel task you must attach the wheel through the task’s serverless Environment and Libraries and point it to a wheel stored in Workspace files or a Unity Catalog volume.
See if this link has the instructions you are looking for - https://docs.databricks.com/aws/en/compute/serverless/dependencies
https://docs.databricks.com/aws/en/jobs/python-wheel
https://docs.databricks.com/aws/en/jobs/how-to/use-python-wheels-in-workflows
Pradeep Singh - https://www.linkedin.com/in/dbxdev
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-12-2026 09:12 PM
Pradeep Singh - https://www.linkedin.com/in/dbxdev