chore: Use Maven Central mirror and cache for WireMock in Windows CI#260
Merged
Conversation
The Windows CI job downloaded the WireMock standalone jar from Maven Central on every run. Maven Central blocks GitHub's shared runner IPs for automated consumption, returning a 403 Terms of Service error. Switch the download to the Google-hosted Maven Central mirror, which serves the identical artifact without that limit, and cache the jar with actions/cache so it is only fetched on a cache miss. The existing checksum verification still runs against both fresh and cached jars.
keelerm84
changed the title
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
2 participants
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.
Summary
The Windows CI job downloaded the WireMock standalone jar directly from Maven Central (
repo1.maven.org) on every run. Maven Central blocks GitHub's shared runner IPs for automated consumption, returning an HTTP 403 Terms of Service error and failing the build.This change:
maven-central.storage-download.googleapis.com), which serves the identical artifact and is not subject to the per-IP block.actions/cachekeyed on the WireMock version, so it is only fetched on a cache miss.The existing checksum verification step is unchanged and now validates both freshly downloaded and cache-restored jars.
A code search across the
launchdarklyandlaunchdarkly-labsorgs confirmsphp-server-sdkis the only repository downloading the WireMock standalone jar this way, so no other repos need the fix.Note
Low Risk
CI-only change to artifact download and caching; runtime SDK behavior is unchanged.
Overview
Fixes Windows CI failures when fetching the WireMock standalone JAR from
repo1.maven.org(HTTP 403 from Maven Central’s automated-use limits on shared GitHub runner IPs).The workflow now caches
wiremock.jarwithactions/cache@v4(keyed to WireMock 2.31.0) and only runs the download step on a cache miss. The download URL moves to the Google-hosted Maven Central mirror (maven-central.storage-download.googleapis.com) for the same artifact. The existing SHA-256 checksum step still runs for both freshly downloaded and restored jars.Reviewed by Cursor Bugbot for commit 486b81a. Bugbot is set up for automated code reviews on this repo. Configure here.