-
Notifications
You must be signed in to change notification settings - Fork 240
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
JFROG_CLI_RELEASES_REPO doesn't work on private Artifactory #2231
Comments
I also found the same problem,I am trying to lower the jf-cli version. |
Hello, any update ? This problem is blocking us. |
same problem here, tested on jfrog-cli-2.52.2.x86_64.rpm |
All, |
Hello @usinelogicielle, @evil-of-blad and @biernatt , thank you for reaching out! The information regarding the jfrogcli-maven-remote repository pointing to 'https://oss.jfrog.org/artifactory/oss-release-local' is based on a legacy setup. Our current methodology employs a different approach. By utilizing the 'jf options' command, you'll notice that the required configuration for JFROG_CLI_RELEASES_REPO is to proxy to 'https://releases.jfrog.io', not 'https://oss.jfrog.org/artifactory/oss-release-local'. The 'https://releases.jfrog.io' serves as a proxy from where all necessary resources for our workflows can be downloaded seamlessly. When supplying the server ID (token_artifactory_serverid) and setting JFROG_CLI_RELEASES_REPO to 'https://releases.jfrog.io', the URL will be automatically constructed as follows: Which is the correct URL for the requested resource. We trust this solution resolves the issue you've encountered. If you have any further questions or if the solution didn't fix your problem, please don't hesitate to let us know. |
Hi @eranturgeman, I understand the change. But the variable documentation would have to be modified. It says that JFROG_CLI_RELEASES_REPO corresponds to a repository. And not to an Artifactory server. I think this would work, but it distorts the naming convention to have a repository named "local" when it's a remote. |
We resolve the case by adding proxy repo to Jfrog oss-release-local in our Antifactory |
We had this issue as well... We did proxy https://releases.jfrog.io/artifactory/oss-release-local, and got the 404 failure After adding a proxy to https://releases.jfrog.io, the issue was resolved |
This solution sounds more linke a workaround as it takes all flexability structuring and naming the source repository. I would favour setting up any mvn repository pointing to https://releases.jfrog.io/artifactory/oss-release-local and the cli not to add "artifactory/oss-release-local" to the request. Example:
|
Describe the bug
Configuring the new environment variable JFROG_CLI_RELEASES_REPO,
and trying using "jfrog mvn".
Jfrog can't download the build-info-extractor-maven3 jar because the URL is wrong.
It seems Jfrog add repo name from JFROG Artifactory.
Current behavior
jfrogcli-maven-remote is the name of our remote repository pointing to "https://oss.jfrog.org/artifactory/oss-release-local"
The URL to download the jar is wrong
https://<ARTIFACTORY_HOST>/artifactory/jfrogcli-maven-remote/artifactory/oss-release-local/org/jfrog/buildinfo/build-info-extractor-maven3/2.41.5/build-info-extractor-maven3-2.41.5-uber.jar => https://<ARTIFACTORY_HOST>/artifactory/jfrogcli-maven-remote/org/jfrog/buildinfo/build-info-extractor-maven3/2.41.5/build-info-extractor-maven3-2.41.5-uber.jar
Reproduction steps
Already explained in Current behavior
Expected behavior
Construct the good URL of personnal remote repository
JFrog CLI version
2.48.0
Operating system type and version
OS/Arch: linux/amd64
JFrog Artifactory version
7.55.3 rev
JFrog Xray version
3.62.4
The text was updated successfully, but these errors were encountered: