RTECO-992 - Fix uv build command build-info and update jfrog-cli-artifactory dependency#3485
Merged
Merged
Conversation
agrasth
added
the
safe to test
itsmeleela
approved these changes
May 14, 2026
naveenku-jfrog
approved these changes
May 14, 2026
agrasth
force-pushed
the
fix/uv-build-command-buildinfo
branch
from
8dbb1a0 to
5b96a4e
Compare
agrasth
added
safe to test
…factory dependency - Update jfrog-cli-artifactory to pick up fix for jf uv build build-info (restores module+dependencies, clears artifacts following Maven convention) - Fix TestUvArtifactTypeIsExtension: verify artifact types via jf uv publish instead of jf uv build since build uploads nothing to Artifactory
agrasth
force-pushed
the
fix/uv-build-command-buildinfo
branch
from
5b96a4e to
4ff81f4
Compare
agrasth
added
safe to test
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 free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Problem
Three UV tests were failing after jfrog-cli-artifactory PR #438 was merged:
TestUvBuild—"[]" should have 1 item(s), but has 0(no module in build-info)TestUvArtifactTypeIsExtension—Should NOT be empty, but was []TestUvCustomModule—Should NOT be empty, but was []PR #438 skipped build-info entirely for
jf uv build, but the tests expected at least a module to exist.Fix
jfrog-cli-artifactory (PR #449)
Restored build-info collection for
jf uv buildfollowing Maven's convention for non-deploy goals:uv build)uv_test.go
TestUvArtifactTypeIsExtensionwas checking artifact types fromjf uv build— but sincebuildno longer records artifacts (consistent withTestUvBuild's existing assertion), the test is updated to verify artifact types viajf uv publishinstead.Changes
go.mod/go.sum: updatedjfrog-cli-artifactoryto pick up the fixuv_test.go:TestUvArtifactTypeIsExtensionnow runsbuildthenpublishbefore checking artifact types