Uh oh!
There was an error while loading. Please reload this page.
Print relative path to uploaded artifact and with deterministic order - #2539
Merged
Conversation
denik
requested review from
andrewnester, anton-107, pietern and shreyas-goenka
as code ownersMarch 20, 2025 13:51
denikforce-pushed
the
denik/artifacts-upload-determ
branch
from
March 20, 2025 13:54
eb7403e to
e486c45Comparedenik
enabled auto-merge
March 20, 2025 14:00
andrewnester
approved these changes
Mar 20, 2025
denik added a commit
that referenced
this pull request
Mar 20, 2025
Follow up to #2539 Since these are "slow" tests, PR checks did not catch them.
github-merge-queueBot
pushed a commit
that referenced
this pull request
Mar 21, 2025
Follow up to #2539 Since these are "slow" tests, PR checks did not catch them.
deco-sdk-taggingBot
added a commit
that referenced
this pull request
Mar 26, 2025
## Release v0.245.0 ### Bundles * Processing 'artifacts' section is now done in "bundle validate" (adding defaults, inferring "build", asserting required fields) ([#2526])(#2526)) * When uploading artifacts, include relative path in log message ([#2539])(#2539)) * Added support for clusters in deployment bind/unbind commands ([#2536](#2536)) * Added support for volumes in deployment bind/unbind commands ([#2527](#2527)) * Added support for dashboards in deployment bind/unbind commands ([#2516](#2516)) * Added support for registered models in deployment bind/unbind commands ([#2556](#2556)) * Added a mismatch check when host is defined in config and as an env variable ([#2549](#2549)) * New attribute on artifacts entries: `dynamic_version`. When set to true, it patches the wheel with dynamic version suffix so it is always used by Databricks environments, even if original wheel version is the same. Intended for development loop on interactive clusters. ([#2520](#2520))
denik added a commit
that referenced
this pull request
May 20, 2026
…#2539) ## Changes - When printing "Uploading name.whl..." message, include path relative to sync root in name. Previously it only included filename. The path separator is always forward slash. - Print those messages in deterministic order. ## Why Mainly to simplify and get more value from acceptance tests, especially those where multiple wheels are involved. Printing relative path also gives user better idea of what's going on. ## Tests Updated tests where we had to work around lack of determinism.
denik added a commit
that referenced
this pull request
May 20, 2026
Follow up to #2539 Since these are "slow" tests, PR checks did not catch them.
denik pushed a commit
that referenced
this pull request
May 20, 2026
## Release v0.245.0 ### Bundles * Processing 'artifacts' section is now done in "bundle validate" (adding defaults, inferring "build", asserting required fields) ([#2526])(#2526)) * When uploading artifacts, include relative path in log message ([#2539])(#2539)) * Added support for clusters in deployment bind/unbind commands ([#2536](#2536)) * Added support for volumes in deployment bind/unbind commands ([#2527](#2527)) * Added support for dashboards in deployment bind/unbind commands ([#2516](#2516)) * Added support for registered models in deployment bind/unbind commands ([#2556](#2556)) * Added a mismatch check when host is defined in config and as an env variable ([#2549](#2549)) * New attribute on artifacts entries: `dynamic_version`. When set to true, it patches the wheel with dynamic version suffix so it is always used by Databricks environments, even if original wheel version is the same. Intended for development loop on interactive clusters. ([#2520](#2520))
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
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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
Why
Mainly to simplify and get more value from acceptance tests, especially those where multiple wheels are involved.
Printing relative path also gives user better idea of what's going on.
Tests
Updated tests where we had to work around lack of determinism.