Sporadic 502 Bad Gateway, 500 Internal Server Error for maven-metadata.xml resources

Event timeline

How this incident unfolded, from the official status page.

1. Investigating

   almost 5 years ago

   Gradle

   We are currently investigating this issue.

2. Investigating

   almost 5 years ago

   Gradle

   We are continuing to investigate this issue.

3. Identified

   almost 5 years ago

   Gradle

   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.

4. Identified

   almost 5 years ago

   Gradle

   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.

5. Monitoring

   almost 5 years ago

   Gradle

   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.

6. Resolved

   almost 5 years ago

   Gradle

   JCenter is now back online, systems are fully operational.

7. Postmortem

   almost 5 years ago

   Gradle

   Postmortem can be found at [https://blog.gradle.org/plugins-jcenter](https://blog.gradle.org/plugins-jcenter)