Skip to content

Clarify JFROG_CLI_RELEASES_REPO env var documentation#3589

Open
rickbrouwer wants to merge 1 commit into
jfrog:masterfrom
rickbrouwer:fix-jfrog-cli-releases-repo
Open

Clarify JFROG_CLI_RELEASES_REPO env var documentation#3589
rickbrouwer wants to merge 1 commit into
jfrog:masterfrom
rickbrouwer:fix-jfrog-cli-releases-repo

Conversation

@rickbrouwer

Copy link
Copy Markdown
  • All tests have passed. If this feature is not already covered by the tests, new tests have been added.
  • The pull request is targeting the master branch.
  • The code has been validated to compile successfully by running go vet ./....
  • The code has been formatted properly using go fmt ./....

The env var docs only stated that the remote should proxy https://releases.jfrog.io, without mentioning that the CLI appends 'artifactory/oss-release-local/' to the request URL. This caused confusion at our end configuring a remote pointing at a sub-path or a non-standard upstream. Spell out the exact URL that gets built and the root-proxy requirement.

@github-actions

github-actions Bot commented Jul 6, 2026

Copy link
Copy Markdown
Contributor

All contributors have signed the CLA ✍️ ✅
Posted by the CLA Assistant Lite bot.

@rickbrouwer

Copy link
Copy Markdown
Author

I have read the CLA Document and I hereby sign the CLA

@rickbrouwer

Copy link
Copy Markdown
Author

recheck

Signed-off-by: Rick Brouwer <rickbrouwer@gmail.com>
@rickbrouwer rickbrouwer force-pushed the fix-jfrog-cli-releases-repo branch from b58e617 to 35cca69 Compare July 7, 2026 16:09
@rickbrouwer rickbrouwer changed the title Clarify JFROG_CLI_RELEASES_REPO env var documentation Clarify JFROG_CLI_RELEASES_REPO env var documentation Jul 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant