The build setup running longer than expected
Platform Notice: Cloud Only - This article only applies to Atlassian products on the cloud platform.
Summary
This article talks about the scenario when the build setup is running longer than expected
Solution
Possible causes:
The repository or the image build size is too large
Troubleshooting Steps:
Try to clone the repository and pull the image locally and observe the time taken. Is the time taken similar to its taking on the Pipeline?
Command to pull the image: docker pull [OPTIONS] NAME[:TAG|@DIGEST]
Command to clone the repository:
Clone over HTTPS
1
$ git clone https://username@bitbucket.org/teamsinspace/documentation-tests.gitClone over SSH
1
$ git clone ssh://git@bitbucket.org:teamsinspace/documentation-tests.gitYES
The build setup time includes the repository clone and image pull duration among other things. Try the following.
Reduce the repository size using the steps on Reduce repository size page.
Use the lower depth level to clone the repository in the Pipeline as instructed on depth (Git only) section on Configure bitbucket-pipelines.yml page
Reduce the build image size using the guidelines on How to Reduce Docker Image Size page.
NO
Raise a Support Ticket and share the Pipeline build URL from bitbucket.org
Was this helpful?