Cleaning up removed SVN branches

[Magnus Granander]

Hi!

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 http://svn.etraveli.net/repos/svn/branches/b-rel-9-1.
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 http://svn.etraveli.net/repos/svn/branches/b-rel-9-1-patch-1.
        at com.atlassian.bamboo.repository.svn.SvnRepository.getLastCommit(SvnRepository.java:1941)
        at com.atlassian.bamboo.plan.branch.BranchExpiryJob.execute(BranchExpiryJob.java:86)
        at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
        at com.atlassian.bamboo.quartz.SystemAuthorizedThreadPool$1.run(SystemAuthorizedThreadPool.java:38)
        at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:525)

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.

[Marcin Gardias]

It's obviously not correct. I've created this bug: https://jira.atlassian.com/browse/BAM-13116