JFrogDotnetCore@1 "push" command does not use DotNet core

[DavidRadoorHummel]

Describe the bug

The task JFrogDotnetCore@1 with the command "push" does not use DotNet Core, but simply uses JFrog CLI (only). This means that any DotNet core specific arguments are not used.

For example:

- task: JFrogDotnetCore@1
  inputs:
    command: 'push'
    arguments: '--skip-duplicate'
    artifactoryConnection: ${{ parameters.artifactoryConnection }}
    targetDeployRepo: '${{ parameters.deployRepo }}'
    pathToNupkg: '${{ parameters.pathToNupkg }}'
    collectBuildInfo: true
    includeEnvVars: true
    buildName: '${{ parameters.buildName}}'
    buildNumber: '${{ parameters.buildNumber}}'
  displayName: 'Publish Nuget Package(s) To Artifactory'
  continueOnError: false

And the output command in the pipeline is:

/__t/jf/2.44.1/x64/jf rt u "/__w/29/a/NugetPackages/MyPackage.*.nupkg" "nuget-snapshot-local" --server-id="MyId" --flat="true" --build-name="MyBuild" --build-number="1"

Notice that it is not jf rt dotnet nuget push but simply jf rt u. Additionally, the argument --skip-duplicate is ignored.

Current behavior

The task JFrogDotnetCore@1 is not using "DotNet core" with JFrog CLI, but simply uses JFrog CLI and ignores DotNet specific arguments.

Reproduction steps

• Create a pipeline that uploads a nuget package with the task JFrogDotnetCore@1 and the push command
• Notice how, in the pipeline output, it does not use jf rt dotnet``

Expected behavior

The task JFrogDotnetCore@1 uses jf rt dotnet command and uses the arguments specified.

Azure DevOps extension name and version

2.8.0 (Latest)

JFrog CLI version

2.44.1 x64

Operating system type and version

Windows 10

JFrog Artifactory version (if relevant)

No response

JFrog Xray version (if relevant)

No response

JFrog Distribution version (if relevant)

No response

[WilliBarankin]

Confirm the same behavior for JfrogNuget execution for push command. As it is seen in the code, 'rt u' is defined as command for uploading of nuget package
const cliUploadCommand = 'rt u';
This impacts us a lot. Sure we can use CLI command like 'jf nuget push' but we are interested in using service connection instead of creating local config files each time when pipeline executes.
As a side effect of this we see that using JfrogNuget/DotnetCore extensions for publishing package allow rewriting existing packages of the same version. Though 'jf nuget push' does not allow rewriting.

Any updates on the bug status? Any comments from the extension maintainers about why not native command is used here?

[shuvadipc]

Thanks for reporting these. Both of these are not supported by JF CLI and are candidate for future feature enhancements. Changing the label from bug to the feature request and will be considered in the backlog.