Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Public Docker Hub image: androidsdk, build setup is very slow

I have setup pipelines to run some android tests and make some builds, but it seems the build setup step is very slow because of the docker image which should be cached by bitbucket, as I'm using androidsdk/android-31. Duration of the build setup step is 1.5-2 minutes.
One thing I've noticed is that if I tried the same setup in a different repo, with the same settings, the build setup time is < 20s. 
This is the code in bitbucket-pipelines: image: androidsdk/android-31
Do you have any suggestions for improving the build setup part? 

1 answer

0 votes
Theodora Boudale
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Sep 19, 2022

Hi Bogdan and welcome to the community!

The build setup is doing additional things, like cloning the repo and downloading caches.

Did you watch a build of this repo as it was running, and was it showing to pull images for the majority of these 1.5-2 minutes?

If so, I would suggest creating a ticket with the support team so we can check the Pipelines build log and additional logs from our side, in order to troubleshoot.

If the setup is taking a lot of time on the clone part, and if you are running builds on branches or tags, you can try setting up in your bitbucket-pipelines.yml file the depth of the clone (which is 50 by default) to e.g. 1 if you only need the last commit for the builds:

If the long setup time has to do with caches, you could remove caches, but then your build may take a longer time downloading dependencies.

If the culprit seems to be pulling the Docker image, please create a ticket and provide the URL of a build with this issue and we will look into it. You can open a ticket via, in "What can we help you with?" select "Technical issues and bugs" and then Bitbucket Cloud as product.

Kind regards,

Suggest an answer

Log in or Sign up to answer
Site Admin
AUG Leaders

Atlassian Community Events