Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Installing from Artifactory seems stuck at version 2.37.1 #32

Closed
larsskj opened this issue Jul 1, 2024 · 2 comments · Fixed by jfrog/jenkins-jfrog-plugin#95
Closed
Labels
bug Something isn't working

Comments

@larsskj
Copy link

larsskj commented Jul 1, 2024

Describe the bug

We have setup the JFrog plugin to install the latest version of the jf CLI from our Artifactory SaaS instance - just as described in the plugin documentation: A generic repo connected to JFrog - which shows 'Remote Artifactory detected' - and the tools setup in Jenkins points to this repo and the version field is empty - which should mean latest version.

Current behavior

For some reason, Artifactory doesn't update the CLI client: The version found at <reponame>/v2-jf/[RELEASE]/jfrog-cli-linux-amd64/jf is stuck at 2.37.1. This is causing issues as the JFrog platform is being upgraded.

Reproduction steps

Download the RELEASE artifact from the above path: It invariably delivers 2.37.1.

Expected behavior

We would expect to get the latest version as per documentation.

JFrog plugin version

1.5.0

JFrog CLI version

2.37.1 :-)

Operating system type and version

Linux / Windows / Docker / Podman / Kubernetes

JFrog Artifactory version

Latest SaaS

JFrog Xray version

Latest SaaS

@larsskj larsskj added the bug Something isn't working label Jul 1, 2024
@yahavi
Copy link
Collaborator

yahavi commented Jul 1, 2024

@larsskj
Thank you for reporting this issue.

To resolve it, please uncheck the Store Artifacts Locally option in the remote repository configuration:
image

Please let me know if that helped and we will add it to the documentation.

@larsskj
Copy link
Author

larsskj commented Jul 2, 2024

Hi @yahavi ,

You're right - that did the trick: We do get the latest version now. It would probably be a good idea to update documentation. :-)

Thank you for solving this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants