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,466,187
Community Members
 
Community Events
176
Community Groups

Feature branch deletion

Our feature branches are becoming disabled in the corresponding Bamboo plan when they're merged and deleted in the repository.  They aren't being fully deleted however!  This is problematic for us because we're on the Start license with a limit of 10 jobs (but would be a problem anyway with unlimited jobs).

The main unusual thing with our setup is that Bamboo runs on an Azure VM that only runs around Office hours - so possibly 'cron' or equivalent jobs if there are any may never execute.

Is there a good way to diagnose something like this?

1 answer

0 votes

At plan level configuration you should use aggressive branch expiration settings: 

Screen Shot 2018-04-17 at 18.45.53.png

By default Bamboo removes disabled plan branches at 3 AM local time. But it's possible to start Bamboo with system property 

-Dbamboo.branch.expiry.schedule=8:15

to run expiry at 8:15 AM local time 

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events