Troubleshooting Bitbucket Cloud Pipelines build with the error message: "The commit could not be found in the cloned repository. This can be caused by using force push or not having a deep enough clone"
Platform Notice: Cloud Only - This article only applies to Atlassian products on the cloud platform.
Summary
This KB article addresses a specific issue encountered during a failed pipeline build. The error message states, "The commit could not be found in the cloned repository. This can be caused by using force push or not having a deep enough clone."
Diagnosis
To determine if the build is a rerun or a new build, follow these steps:
Rerun builds:
Go to your repository > Click Pipelines tab.
Apply the filter for Trigger type and select "rerun/manual". This will display the list of builds that were either rerun or manually triggered.
If the failed build is shown in the list, it will likely be a rerun.
New builds:
Open the failed build that you want to diagnose.
Click on the commit that triggered the build.
Check for error messages indicating that the commit couldn't be located or a warning message stating that the commit is unreachable with any branch.
Cause
This problem occurs when a user initiates a force push or tries to rerun a build older than 50 commits. The issue happens because a force push in the affected repository replaces the previous commit hash. Consequently, when the pipeline attempts to locate the overwritten commit during execution, it fails. Similarly, trying to rerun over 50 commits of old builds is an issue because the pipeline build utilises a shallow clone.
Solution
Before applying any workaround, it's essential to identify the cause of the build failure. Once you have identified the reason, you can follow the appropriate solution provided below:
For rerun builds:
To enable a full-depth clone in the pipeline and ensure a complete clone is performed for each build, you can use the following configuration:
1
2
3
4
5
6
7
8
clone:
depth: full
pipelines:
default:
- step:
script:
- ls $BITBUCKET_CLONE_DIRPlease refer to our Git clone behavior documentation article for more information on enabling full-depth clones, or use the above example as a reference.
For new builds:
Unfortunately, if the build has already failed and you don't have the necessary commit history, there is no direct way to rerun the build. The only option would be to have someone with access to the previous commit history push the missing commit back to the remote repository. Without that commit, the build can't be rerun.
If you are still encountering issues after following this troubleshooting article, please raise a support ticket or raise a community support ticket for further assistance.
Description | Troubleshooting Bitbucket Cloud Pipelines build with the error message: "The commit could not be found in the cloned repository. This can be caused by using force push or not having a deep enough clone" |
|---|---|
Product | Bitbucket Cloud |
Was this helpful?