Can't publish the .NET/NuGet packages with build information via 'jf dotnet nuget push' command
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 595
- Forks
- 307
- Avg merge
- 4d 17h
- Merged PRs (30d)
- 17
Description
Describe the bug
If we use the command:
jf dotnet nuget push *.nupkg --source "MyArtifact" --build-name="xxx" --build-number="x" to push the .NET packages to the Artifactory, we can't find the build information under Builds,
But use the command:
jf rt u "*.nupkg" $nuget-repo-name --build-name="sample_project_build_info" --build-number="1.0.1" can push the .NET packages to the Artifactory with the build information
Current behavior
We use the command:
jf dotnet nuget push *.nupkg --source "MyArtifact" --build-name="sample_project_build_info" --build-number="1.0.1" to push the .NET packages to the Artifactory, we can't find the build information under Builds,
But use the command:
jf rt u "*.nupkg" $nuget-repo-name --build-name="sample_project_build_info" --build-number="1.0.1" can push the .NET packages to the Artifactory with the build information
Reproduction steps
jf dotnet-config --server-id-resolve xxx --repo-resolve xxxx
jf dotnet restore --build-name=xxx --build-number=x
jf dotnet pack --configuration Release --output ./ --build-name=xxx --build-number=x
jf dotnet nuget push *.nupkg --source "MyArtifact" --build-name="xxx" --build-number="x"
jf rt bp xxx x
Expected behavior
Can use the command jf dotnet nuget push *.nupkg --source "MyArtifact" --build-name="sample_project_build_info" --build-number="1.0.1" to publish the packages with build information
JFrog CLI version
jf version 2.93.0
Operating system type and version
macOS Tahoe 26.3
JFrog Artifactory version
7.133.10
JFrog Xray version
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the documented sequence with jf dotnet restore, jf dotnet pack, jf dotnet nuget push, and jf rt bp, comparing it with jf rt u. Trace the dotnet nuget push entry point and build-information handling; done means the push produces build information visible under Artifactory Builds.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100