Description
You Can Now Opt Out of the Bitrise Maven Central Proxy with an Environment Variable - We’ve made it easier to disable the Bitrise Maven Central proxy for builds that need to bypass it.
Highlights:
- Simple Opt-Out: If your build needs to avoid the Bitrise Maven Central proxy, you can now disable it by setting the environment variable
BITRISE_MAVENCENTRAL_PROXY_ENABLED=falsewhen launching the build. - No Script Step Needed: Previously, opting out could require workflow customization. Now, there’s no need to add custom Script Steps - just set the env var and go.
- Takes Precedence Over Other Settings: This environment variable overrides other proxy-related configuration, including the Activate Gradle Mirrors Step.
- Enabled by Default: The Bitrise Maven Central proxy remains enabled for all builds by default to help protect against upstream
429 Too Many Requestsissues, but customers with specific needs now have a straightforward escape hatch. - More Context Available: Read the original announcement and background here: New Gradle Mirrors on Bitrise to Help Avoid Maven Central Rate Limits
Why This Matters
While the Bitrise proxy helps most teams avoid Maven Central and Gradle Plugin Portal throttling, some builds may require direct access for compatibility, debugging, or policy reasons. This change gives those teams an easy and explicit way to opt out without modifying their workflows.
Bottom line: Need to bypass the Bitrise Maven Central proxy? Just set BITRISE_MAVENCENTRAL_PROXY_ENABLED=false at build start, and it will override all other proxy settings automatically.