Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Bug found for cleanup branches by using mercurial/graft?

Inside bamboo configuration "Plan Configuration / Branches", there is an option to delete a branch within the repository after a certain idle time (e.g., 30 days). The rule only looks at the time of the latest source check-in/timestamp. When using a mercurial-graft, from another branch older than 30 days (eg 40 days) will delete the current branch. This behavior isn´t right. The rule must check the activity which was performed in the current branch and not the timestamp on latest source check-in.

1 answer

1 accepted

0 votes
Answer accepted

Hello Torsten,

I think you are right. From your description, It seems you've stumbled into this bug: [BAM\-18460\] New plan branch is automatically deleted due to last commit date from the newly created branch.

As a workaround, I do suggest that when you create a new branch from a commit that is older than your expiry interval, please add a simple small commit to your new branch. The expiry job is usually configured to run at 3 AM so you will probably have time to add the new commit before the job is run. It doesn't look like a beautiful solution but is something you can do until we fix that bug.

Another possible workaround is to increase your branch expiry interval to a bigger value to cover your scenario.

I hope that helps!

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Bamboo

Bamboo 101 Video

G’day Community! As we gear up to introduce Bamboo Data Center to the world, we wanted to make sure that we shared a bit more about Bamboo, the product. Our team has put together an overview video ...

179 views 4 6
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you