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.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Bamboo 5.9 will no longer be supported after June 12, 2017. What does this mean? As part of our End of Life policy, Atlassian supports major versions for two years after the first major iteratio...
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!
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