Bamboo was unable to extract changes between revisions
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
Build summary tab in bamboo build shows an error message "Bamboo was unable to extract changes between revision e08e952ab195dc58bde1da8a2863bb728f9a18eb and 1342df275326e75c8a264495379791d7457d924b" in the field where the the commit message should appear.
Environment
The issue was observed on Bamboo 9.2.7, but other versions may be affected.
Diagnosis
The build summary page of bamboo build shows below errors in the field which should ideally show the commit message with diff.
"Bamboo was unable to extract changes between revision e08e952ab195dc58bde1da8a2863bb728f9a18eb and 1342df275326e75c8a264495379791d7457d924b"
This is observed if the plan is configured with a git based repository (Bitbucket, Github, etc.).
Cause
Most common explanation for the issue would be a git force push or a git rebase on the repository side. This is how Bamboo handles history rewrites.
From Bamboo's perspective, if a commit disappeared (older commit not attached to a branch anymore), there is no way for Bamboo to tell how did that happen.
As a result, it updates the commit to the current HEAD and hence the above message shows up in the build summary instead of commit message with diff.
Solution
From functionality standpoint this does not impact the builds as it is executed with correct code revision (latest commit id). However, it is expected to show the message "Bamboo was unable to extract changes between revision e08e952ab195dc58bde1da8a2863bb728f9a18eb and 1342df275326e75c8a264495379791d7457d924b" in the build summary page.
Was this helpful?