jfrog / jfrog-azure-devops-extension

Apache License 2.0
47 stars 62 forks source link

Ability to always use the latest available Jfrog-CLI version through Azure DevOps Plug in #374

Open manojkumarm-git opened 1 year ago

manojkumarm-git commented 1 year ago

This is regarding the Github issue related to the JFrog Azure DevOps plugin https://github.com/jfrog/jfrog-azure-devops-extension/issues/372. The JFrog plugin tasks to use the latest version of CLI in the pipeline.

The latest available JFrog CLI is on version 2.34.1 as per the https://releases.jfrog.io/artifactory/jfrog-cli/v2-jf/ but when running the pipeline, it's pulling the old default version. But it should pull the latest version If I am not specifying any version.

Sample logs from the pipeline are attached for reference.

Screenshot 2023-02-06 at 9 46 13 AM 1

What is the expected behavior?

While running the JFrog Azure DevOps pipeline, the plugin should pull the latest version of JFrog CLI.

JFrog Azure DevOps extension version: 2.3.0

Possible workaround:

In the JFrog Azure DevOps pipeline, we can use of install custom version option as below.

      `- task: JFrogToolsInstaller@1
      inputs:
      artifactoryConnection: 'cloud'
      cliInstallationRepo: 'jf-remote'
      installCustomVersion: true
      cliVersion: '2.34.1'`
fourpastmidnight commented 6 months ago

This has bitten me, too. I mean, there's a task to get the JFrog CLI...but, when you ship a new version of this extension, you don't update the CLI packaged with it?? What gives? Really annoying.