jfrog
Nuget builds are recognized as type 'Generic' while publishing it using JFrog CLI
Case description: While performing the NuGet builds using JFrog CLI, especially with the jf rt u command the published builds are identified as GENERIC builds at the Artifactory’s end. Steps to reproduce the case:
-
Install JFrog Cli: 2.57.1
-
As the customer uses a Nuget package I have Clone the project called dotnet-example/single-example from the JFrog GitHub URL.
-
Once the project is cloned, change to the directory where the .cs file is present which is the root directory.
-
In Jfrog Artifactory creates a Nuget virtual repository including default deployment to local and resolve packages from the remote repository.
-
In the terminal to configure the Jfrog artifactory use the command “jf c add”
-
To configure the specific repository created in step 4 use “jf dotnet-config --repo-resolve=<NUGET_RESOLUTION_REPOSITORY>”
-
Restores the dependencies and tools of the project from Artifactory “ jf dotnet restore --build-name=my-build --build-number=1”
-
Execute the 'audit' scan command. “ jf audit”
-
Build the project with dotnet and resolve the project dependencies from Artifactory. “dotnet pack”
-
Upload the packages to a NuGet repository in Artifactory: jf rt u "*.nupkg" <NUGET_DEPLOYMENT_REPOSITORY>/ --build-name=my-build --build-number=1
-
Collect environment variables and add them to the build info. jf rt bce my-build 1
-
Publish the build info to Artifactory. jf rt bp my-build 1
Expected behavior:
Though it is an expected behavior that the build info would be identified as GENERIC while using the generic upload commands, rather than package tools like “jf mvn” “jf gradle” etc., it would be useful if the generic upload commands are allowed to be executed with an additional argument in place.
For example: --build-type
$ jf rt u
