Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,463,473
Community Members
 
Community Events
176
Community Groups

Delete after merging fails to delete feature branch (Clean up failed)

Edited

We run a Bitbucket server v7.20.0 and merge feature branches by pull requests into the master branch. We use the "Delete after merging" feature to let Bitbucket clean up the feature branches after they have been merged into master.

However on an irregular basis this operation fails. The code is merged successfully, but the feature branch doesn't get deleted. The error message reads: "Clean up failed. The pull request was merged, but source branch couldn't be deleted". We then have to delete the branches manually, which of course defeats the purpose.

Bitbucket-Delete-FeatureBranch-Error.png

As the documentation explains (https://confluence.atlassian.com/bitbucketserver0720/merge-a-pull-request-1116281190.html), certain criteria must be met in order for this feature to work. All of them apply to our configuration (it's not the default branch, permissions are set and no other pull requests are open). The issue happens on and off for the same user on the same repository.

I haven't found any open issues or related articles about this. Does anyone know what's the problem here and how to fix it?

0 answers

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events