Could not resolve all files for configuration

Question & Answer Builds
,
1

Description of the issue

The issue is intermittent, and the jar on which it stop is different on each issues

Environment:

Its Android build, and use Android & Docker, Ubuntu 16.04. The log is from step install-missing-android-tools version 2.0.2.

Reproducibility

  • Does a ā€œRebuildā€ help? (You can trigger a rebuild from the Buildā€™s page, by clicking the ā€œRebuildā€ button in the top right corner of a finished build) : NO
  • Does a rebuild without caches help? (You can remove the Cache:Pull and Cache:Push steps temporarily to not to use the cache, or you can delete all the caches on the Settings tab of the app. : NO
  • Does the issue happen sporadically, or every time? : Sporadically
  • Does upgrading the build Step to the latest version help? : NO
  • When did the issue start? : sporadically, canā€™t remember since when

Local reproduction

The build run succesfully on local machine (Mac High Sierra)

Local reproduction: Linux / Android (docker based) stack builds

Not tested

Build log

`Download https://jcenter.bintray.com/org/apache/maven/doxia/doxia-site-renderer/1.1.2/doxia-site-renderer-1.1.2.jar
FAILURE: Build failed with an exception.

  • What went wrong:
    A problem occurred configuring root project ā€˜srcā€™.

Could not resolve all files for configuration ā€˜:classpathā€™.
Could not download doxia-module-xhtml.jar (org.apache.maven.doxia:doxia-module-xhtml:1.1.2)
Could not get resource ā€˜https://jcenter.bintray.com/org/apache/maven/doxia/doxia-module-xhtml/1.1.2/doxia-module-xhtml-1.1.2.jarā€™.
Could not GET ā€˜https://jcenter.bintray.com/org/apache/maven/doxia/doxia-module-xhtml/1.1.2/doxia-module-xhtml-1.1.2.jarā€™. Received status code 504 from server: Gateway Time-out
Could not download doxia-core.jar (org.apache.maven.doxia:doxia-core:1.1.2)
Could not get resource ā€˜https://jcenter.bintray.com/org/apache/maven/doxia/doxia-core/1.1.2/doxia-core-1.1.2.jarā€™.
Could not GET ā€˜https://jcenter.bintray.com/org/apache/maven/doxia/doxia-core/1.1.2/doxia-core-1.1.2.jarā€™. Received status code 504 from server: Gateway Time-out
Could not download commons-digester.jar (commons-digester:commons-digester:1.6)
Could not get resource ā€˜https://jcenter.bintray.com/commons-digester/commons-digester/1.6/commons-digester-1.6.jarā€™.
Could not GET ā€˜https://jcenter.bintray.com/commons-digester/commons-digester/1.6/commons-digester-1.6.jarā€™. Received status code 504 from server: Gateway Time-out
Could not download httpmime.jar (org.apache.httpcomponents:httpmime:4.1)
Could not get resource ā€˜https://jcenter.bintray.com/org/apache/httpcomponents/httpmime/4.1/httpmime-4.1.jarā€™.
Could not GET ā€˜https://jcenter.bintray.com/org/apache/httpcomponents/httpmime/4.1/httpmime-4.1.jarā€™. Received status code 504 from server: Gateway Time-out

  • Try:
    Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.
  • Get more help at https://help.gradle.org
    BUILD FAILED in 1m 1s
    exit status 1`
2

Hi @fchristysen,

This error comes from jcenter.bintray.com and means thereā€™s a server error on their side. Usually these are just temporary issues on jcenter.bintray.com , the best solution is usually to configure Gradle Cache (How to cache Gradle dependencies).

If youā€™d have any questions just let us know! :slight_smile:

3

Hi Viktor,
Iā€™m not sure if the error comes from their side, since when I try to download the referred jar url in the error log, I could download it successfully.
Sure, Iā€™ll try to look on the Gradle Cache. The issue I reported could occur on different step, in install-missing-android-tools and gradle build step. CMIIW, but the gradle cache will only cache the dependencies from gradle build step, but not the install-missing-android-tools right?

4

It definitely is a bintray issue, itā€™s listed on their status page: http://status.bintray.com/ - http://status.bintray.com/incidents/5qq8yrlyw1vw

Listed as intermittent, meaning not every build might be affected by this, the same resource might or might not work.

1 Like
5

It will cache most from install missing android tools too.

1 Like