We develop and deploy a second fix that allows us to change the repository to which the Plugin Portal redirects. 8.58pm UTC, January 12th Second fix is deployed The first fix turns out to be insufficient. 8.44pm UTC, January 12th First fix is deployed We update the build of the Plugin Portal to not rely on JCenter at all by using repository content filtering and supported metadata sources. However, the hotfix cannot be built and deployed immediately because building the Plugin Portal code requires resolving some plugins from the Plugin Portal itself and JCenter, which failed. 6pm UTC, January 12th We identify a hotfix that will allow the Gradle Plugin Portal to ignore 5xx error codes from JCenter and resolve plugins it hosts entirely. 4.56pm UTC, January 12th Incident opened The outage is acknowledged on the Gradle status page. Outage timeline 4.30pm UTC, January 12th Outage begins Gradle users start noticing that plugin resolution is failing in builds.
Users affected by JCenter outages for project dependencies should also refer to our original blog post about the shutdown of JCenter. This postmortem gives a timeline of the outage, describes the effect on Gradle users, and what actions were taken to further reduce the Gradle Plugin Portal’s reliance on JCenter.įinally, we will also discuss how you can protect your build against such outages.
On January 12th 2022, Gradle users were experiencing issues resolving plugins from the Gradle Plugin Portal because of the outage of JCenter that the Plugin Portal depends on for some of the functionality.
0 kommentar(er)
