Details
-
Bug
-
Resolution: Fixed
-
Low
-
5.11.3
-
Severity 3 - Minor
-
Description
Summary
The last_commit_date stored against a branch in branch_commit_info is set from the AuthorDate instead of the CommitDate of a git commit when JGit (no native git) is used. When native git is used, the last_commit_date is correctly set to the CommitDate.
Steps to Reproduce
- Make a commit to a branch so that the latest commit has a different commit date and author date. E.g. git cherry-pick
- Ensure that no native git capability is defined so that JGit is utilized
- Create a plan in Bamboo using that repository
- Create the branch manually that you committed to
Expected Results
last_commit_date stored against a branch in branch_commit_info is set from the CommitDate
Actual Results
last_commit_date stored against a branch in branch_commit_info is set from the AuthorDate
This can result in branches being detected for deletion earlier than expected.
Workaround
Install native git on the Bamboo Server and define a capability for it at Bamboo Administration > Overview > Server Capabilities
The last_commit_date on an affected branch won't be updated using the CommitDate until a new commit is made.
Attachments
Issue Links
- mentioned in
-
Page Loading...