Bitbucket pipeline is failing with Exceeded build time limit error.

Summary

Solution

Possible causes:

• Time consuming processes in the Pipeline build

Troubleshooting Steps:

Check if there are time consuming processes in the Pipeline build. You can execute the command date +"%T" before and after each build command to find out which processes are taking more time than expected in the Pipeline. Also, test the build locally using command date +"%T" to check which processes are consuming a large number of minutes by following the steps outlined on Debug pipelines locally with Docker page.

Are the processes taking a similar amount of time in the Pipelines and local builds?

YES

• Investigate the processes and identify why they are running for a longer time. Use the online resources based on the command and technology being used to identify what measures can be taken to reduce the process durations.

• Increase the max-time property for the build step or option as mentioned in the

  max-time section of Configure bitbucket-pipelines.yml page

  . (By default this is set to 120 minutes).

• If there is a command waiting for user interaction then make sure these commands are run in a non-interactive mode.

• Increase the build container memory size to 2x, 4x, or 8x as mentioned in the size section of Configure bitbucket-pipelines.yml page

• If the total build time is unable to be reduced, please raise a Support Ticket mentioning the workspace name and the use case of running the step for longer. The Support team will exempt to run the step for more time, if possible.

NO

• Raise a Support Ticket and share the Pipeline build URL from bitbucket.org