Gradle incident
Sporadic 502 Bad Gateway, 500 Internal Server Error for maven-metadata.xml resources
Gradle experienced a minor incident on January 12, 2022 affecting Repository and Gradle's Maven Central redirect, lasting 13h 38m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jan 12, 2022, 04:56 PM UTC
We are currently investigating this issue.
- investigating Jan 12, 2022, 05:02 PM UTC
We are continuing to investigate this issue.
- identified Jan 12, 2022, 07:20 PM UTC
We have a temporary fix being validated in development right now which should resolve a number of issues. We’ll update here when it is deployed so that we can assess whether or not it is enough to get going for now. We will work on a more permanent solution after that in the coming days.
- identified Jan 12, 2022, 08:44 PM UTC
Issue with resolution of `maven-metadata.xml` for plugins hosted on the Gradle Plugin Portal should be resolved. However regular library dependencies of plugins will still fail to resolve because of the underlying failure of JCenter. We are looking at a solution for this as well.
- monitoring Jan 12, 2022, 09:43 PM UTC
We have deployed a second fix that should resolve another set of issues encountered by the JCenter outage. What will remain broken: - Dependencies that only exist in JCenter and were not mirrored to one of Gradle’s repository manager. There is no solution for those unfortunately until JCenter comes back up. We will do a post-mortem and explain our plan to remove that dependency altogether later this week.
- resolved Jan 13, 2022, 06:35 AM UTC
JCenter is now back online, systems are fully operational.
- postmortem Jan 20, 2022, 09:58 AM UTC
Postmortem can be found at [https://blog.gradle.org/plugins-jcenter](https://blog.gradle.org/plugins-jcenter)