Service.gradle.org outage - 30th September 2015

News
1

We are currently experiencing an outage of http://services.gradle.org, which is affecting Gradle Wrapper downloads worldwide. Our upstream provider is suffering a major outage. At this time, they have not provided an ETA on service restoration.

We will post updates here every 30 minutes or as we have them until the issue is resolved. We apologise for the inconvenience.

2

We are currently provisioning a new to service to sit behind http://services.gradle.org which will reinstate Gradle Wrapper downloads.

3

Service has been restored.

We apologise for the inconvenience of the outage.

4

Hi, the problem seems to persist somehow.

We’re using Gradle 1.11 and have the following configuration in gradle/wrapper/gradle-wrapper.properties:

distributionUrl=http\://services.gradle.org/distributions/gradle-1.11-all.zip

I get the following error:

Downloading http://services.gradle.org/distributions/gradle-1.11-all.zip

Unzipping /Users/damien/.gradle/wrapper/dists/gradle-1.11-all/7qd8qq8te5j4f5q9aaei3gh3lj/gradle-1.11-all.zip to /Users/damien/.gradle/wrapper/dists/gradle-1.11-all/7qd8qq8te5j4f5q9aaei3gh3lj
Exception in thread "main" java.lang.RuntimeException: java.util.zip.ZipException: zip file is empty
	at org.gradle.wrapper.ExclusiveFileAccessManager.access(ExclusiveFileAccessManager.java:78)
	at org.gradle.wrapper.Install.createDist(Install.java:44)
	at org.gradle.wrapper.WrapperExecutor.execute(WrapperExecutor.java:126)
	at org.gradle.wrapper.GradleWrapperMain.main(GradleWrapperMain.java:58)
Caused by: java.util.zip.ZipException: zip file is empty

The downloaded ZIP file in indeed empty (0 bytes).

However, when I follow redirections on Curl, I do not have any problem accessing the ZIP:

curl -vL http://services.gradle.org/distributions/gradle-1.11-all.zip

Switching to https fixes the issue but we have hundreds of projects which are now impacted, including some long running maintenance branches we don’t want to update.

Any idea about this problem?

Thanks,
Damien.

5

@Damien_Coraboeuf we have fixed the http endpoint. This should no longer be an issue.

6

I confirm this is fixed. Thanks.

We are now looking actively in using a proxy instead of a direct URL.

7

We’re currently experiencing ongoing issues related to this outage. We are working with our upstream provider to resolve and will post updates as they are available. We apologize for the inconvenience.

8

Issues have been resolved and service should be restored now.