Troubleshooting Bitbucket Pipelines

Summary

This page provides links to articles containing self-serve troubleshooting steps for Pipeline run failures and other common issues.

Solution

• Scenario 1: Builds were successful earlier, but started failing recently

• Scenario 2: Pipeline build failed with Container “Build” exceeded memory limit error

• Scenario 3: Pipelines build failed with Command not found error in the build log

• Scenario 4: Bitbucket pipeline is failing with Exceeded build time limit error

• Scenario 5: Build Technology and Test Framework

• Scenario 6: Pipeline build failed with "Step exceeded processing limits and has timed out" error

• Scenario 7: Artifacts related issues

• Scenario 8: Pipeline build cache-related issues

• Scenario 9: Git Submodule not being cloned in the Pipeline build

• Scenario 10: The build setup running longer than expected

• Scenario 11: The build was not triggered for a particular commit

• Scenario 12: Pipeline build failed with Container “Docker” exceeded memory limit error

• Scenario 13: Pipeline build failed with "unexpected system error that may have left your step half-completed"