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?
At plan level configuration you should use aggressive branch expiration settings:
By default Bamboo removes disabled plan branches at 3 AM local time. But it's possible to start Bamboo with system property
to run expiry at 8:15 AM local time
On 31 May, a GDPR-related change went live in the Bitbucket Cloud API that resulted in users not being able to create or edit Bitbucket Cloud Linked repositories in Bamboo. This API update removed t...
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