Build failed jcenter download

[Aaron_김윤호]

I have a android project repo.

When I run below command on Pipeline, it fail...

./gradlew clean assembleRelease

```

FAILURE: Build failed with an exception.

* What went wrong:

Execution failed for task ':app:lintVitalStageRelease'.

> Could not resolve all files for configuration ':app:lintClassPath'.

    > Could not download groovy-all-2.4.15.jar (org.codehaus.groovy:groovy-all:2.4.15)

        > Could not get resource 'https://repo.maven.apache.org/maven2/org/codehaus/groovy/groovy-all/2.4.15/groovy-all-2.4.15.jar'.

            > Could not GET 'https://repo.maven.apache.org/maven2/org/codehaus/groovy/groovy-all/2.4.15/groovy-all-2.4.15.jar'.

                > Connection reset

```

I tried to add `mavenCentral()` on my `build.gradle` file.

But it's same.

```

FAILURE: Build failed with an exception.

* What went wrong:

Execution failed for task ':app:lintVitalStageRelease'.

> Could not resolve all files for configuration ':app:lintClassPath'.

    > Could not download groovy-all-2.4.15.jar (org.codehaus.groovy:groovy-all:2.4.15)

        > Could not get resource 'https://repo.maven.apache.org/maven2/org/codehaus/groovy/groovy-all/2.4.15/groovy-all-2.4.15.jar'.

            > Could not GET 'https://repo.maven.apache.org/maven2/org/codehaus/groovy/groovy-all/2.4.15/groovy-all-2.4.15.jar'.

                > Connection reset

```

I think that bitbucket cloud has some problem...
What's going on?

[Aaron_김윤호 · Accepted solution]

I solved this problem.

Actually I don't know, But when I increase the jvm build option about the memory size, it works fine.

[Theodora Boudale]

Hi @Aaron_김윤호,

I see that you created another post about this issue earlier this week, and you mentioned that this command works fine in your local machine. My suggestion would be to try debugging this locally with Docker as per the instructions on the following page:

• https://support.atlassian.com/bitbucket-cloud/docs/debug-pipelines-locally-with-docker/

Then please let us know if you see the same error when debugging the build following this doc.

If the build works ok when debugging it locally, my suggestion would be to create a ticket with the Bitbucket Cloud support team and
- provide them the URL of the Pipelines build
- provide also the output of the build when you debugged it locally with Docker
If there is a support ticket open, the engineer working on your case will be able to access the build and assist with further troubleshooting.

Since you are an admin of a workspace on the standard billing plan, you should be able to create a support ticket via https://support.atlassian.com/contact/#/, in "What can we help you with?" select "Technical issues and bugs" and then Bitbucket Cloud as product.

If you have any questions, please feel free to let me know.

Kind regards,
Theodora