Skip to content

Resolve CI Maven and Gradle dependencies through a JFrog mirror - #941

Draft
Jordanh1996 wants to merge 1 commit into
devfrom
ci/resolve-java-deps-through-jfrog
Draft

Jordanh1996 wants to merge 1 commit into
devfrom
ci/resolve-java-deps-through-jfrog

Conversation

@Jordanh1996

Copy link
Copy Markdown
Contributor

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-setup now gets a short-lived read-only token via GitHub OIDC (github-oss-ci provider) and runs jf 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 own settings.xml/init script, which take precedence.)

Tests


🤖 Generated with Claude Code

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Nov 8, 2026

Copy link
Copy Markdown

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

  • Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true

This branch is waiting to be deployed

1 waiting deployment
frogbot — 2935ccb4 Waiting Nov 8, 2026 by Jordanh1996 via scan-pull-request #4779
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