Repository navigation
Resolve CI Maven and Gradle dependencies through a JFrog mirror - #941
Draft
Jordanh1996 wants to merge 1 commit into
Draft
Jordanh1996 wants to merge 1 commit into
Jordanh1996 wants to merge 1 commit into
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Important Draft PR not reviewedDraft PRs are not automatically reviewed by default.
To automatically review draft PRs, update your CodeRabbit configuration: |
This branch is waiting to be deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Background
CI runs on GitHub's shared runners download every Maven and Gradle dependency straight from Maven Central, which rate-limits those runners and fails builds.
Description
On runs inside the jfrog org,
install-and-setupnow gets a short-lived read-only token via GitHub OIDC (github-oss-ciprovider) and runsjf setup maven|gradle --repo oss-maven-virtual, so downloads go through a JFrog mirror of Central and the other public repos the builds use. Fork PRs skip both steps and keep resolving from Central. (Curation and resolution tests are unaffected: they pass their ownsettings.xml/init script, which take precedence.)Tests
devbranch.🤖 Generated with Claude Code