BUILD-12123 Route Develocity plugin resolution through Repox - #332
Conversation
Pass gradle-plugin-repository-* to setup-gradle so Develocity injection does not hit plugins.gradle.org during registry brownouts.
There was a problem hiding this comment.
Pull request overview
Routes Develocity/CCUD Gradle plugin resolution through Repox when Develocity injection is enabled, avoiding direct access to plugins.gradle.org during registry brownouts and related TLS/PKIX failures.
Changes:
- Pass
gradle-plugin-repository-url/username/passwordtogradle/actions/setup-gradlewhenuse-develocity: true. - Point plugin repository resolution at
${repox-url}/artifactory/plugins.gradle.org/using the Artifactory reader credentials already provisioned byconfig-gradle.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Avoid pypi.org during setup-python pip upgrade in the brownout window.
|
Code Review ✅ ApprovedRoutes Develocity plugin resolution and pre-commit pip upgrades through Repox to bypass registry brownouts. No issues found. OptionsAuto-apply is off → Gitar will not commit updates to this branch. Comment with these commands to change the behavior for this request:
Was this helpful? React with 👍 / 👎 | Gitar |



BUILD-12123 Route Develocity plugin resolution through Repox
Summary
use-develocity: true,config-gradlenow passesgradle-plugin-repository-url/username/passwordtosetup-gradle, pointing at${repox-url}/artifactory/plugins.gradle.org/with the Artifactory reader credentials.plugins.gradle.orgduring the BUILD-10865 registry brownout (SSL/PKIX), as seen on sonarlint-intellij CI.config-pipbeforegh-action_pre-commitso pip upgrades resolve via Repox instead ofpypi.org.Related: Slack thread, PREQ-7795
Test plan
config-gradlewithuse-develocity: trueresolvesdevelocity-gradle-pluginfrom Repox (no request toplugins.gradle.org)use-develocity: falseare unchanged