Gradle execution very slow

Bitrise Build Issue Report template

Description of the issue

Please describe the issue here
1 or 2 times a day our gradle build step take a very long time, and (before the avaibility of step timeout) it was killed by the platform timeout
a usual build take less than 10min (gradle step) but often in the afternoon (from UTC+1) it hangs or it’s very slow and never finish


Where did the issue happen?
on Android & Docker, on Ubuntu 18.04

Which build Step causes the issue and which version of the step?

steps-gradle-runner any versions


  • 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) : YES
  • 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. : YES
  • 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? : a long time ago but now it’s more visible and upset some users

Local reproduction

Can it be reproduced on your own Mac/PC by following our local debug guide? Please follow at least the first section (“Testing with a full clean git clone”) to make sure to test the state of the code what will get when it does a git clone in the clean environment! If possible please note which sections you tried.

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

Can it be reproduced by running the build locally, after doing a new git clone of the repository into the /tmp directory and running the build from there with the Bitrise CLI ( )? If no, can it be reproduced with Docker (using the same docker images / environment we use on Related guide: .

Build log

Please copy paste the build’s URL here (or if the issue happens somewhere else then the full logs), or if you can’t share the url / log here then send the url or full log through a private channel (e.g. email - ), with a link to the related Discuss issue.

Hi @CyrilPatrice,
thanks for the report, we will have a look into this asap!


could you please attach your most recent slow and also the most recent fast build urls to let me compare them?

Hi Krisztian,

yesterday it occurs 2 times

before it ends good
Bitrise - Mobile Continuous Integration and Delivery - iOS & Android Build Automation

Hi @CyrilPatrice , i have found something strange:
Based on the build log it seems in the slow builds (02b58a7c0a989706) the test is not able to start your test server.
So in the fast (ce6c7eed31d22cd5) build you can find: => Booting Puma line and it seems your test is communicating with the started server.
While in the slow build there is no => Booting Puma line and the step fails.
Is not it possible that the problem is around starting your test server? Maybe your test tries to start the server and this process has a huge timeout, thats why your failed build takes much more time to finish?

Hi @godreikrisztian,.
Thanks for your help
It’s just a coincidence, the test server is started in a previous step (mock Server)
but do not log before the first call of our tests
for sometimes I increase the verbosity of the gradle step
i will notify you if the issue persist

Hi @CyrilPatrice - did you manage to resolve this issue?

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.