Cleaning up removed SVN branches

We have noticed that when Bamboo tries to run the Expiry Job on a branch that was deleted in SVN it gets the following exception:
2012-10-22 03:00:02,963 INFO [QuartzScheduler_Worker-9] [DefaultErrorHandler] Recording an error: Chain Branch Expiry Job : ITDEV-TRUNK0 : Error while getting last commit on branch
2012-10-22 03:00:03,098 ERROR [QuartzScheduler_Worker-9] [BranchExpiryJob] Error in chain branch expiry
com.atlassian.bamboo.repository.RepositoryException: Error while getting last commit on branch
        at com.atlassian.bamboo.repository.svn.SvnRepository.getLastCommit(
        at com.atlassian.bamboo.plan.branch.BranchExpiryJob.execute(
        at com.atlassian.bamboo.quartz.SystemAuthorizedThreadPool$
        at org.quartz.simpl.SimpleThreadPool$

Is this really the way that things should work? 
To us it seems to be much better to just say "no branch left, well I delete that branch then" instead of keeping old deleted branches associated to the plan. Is there a way to get this behavior? Currently we are starting to work with custom scripts to take care of this and that is not a sustainable solution.

1 answer

0 votes

It's obviously not correct. I've created this bug:

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Monday in Jira Ops

Jira Ops Early Access Program Update #1: Announcing our next feature and a new integration

Thanks for signing up for Jira Ops! I’m Matt Ryall, leader for the Jira Ops product team at Atlassian. Since this is a brand new product, we’ll be delivering improvements quickly and sharing updates...

537 views 0 9
Read article

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you