We use SVN externals extensively. However, Bamboo throws an exceptions stating that authentication failed. I have done everything to confirm that the service account that Bamboo is running under has full access to the SVN repositories.
Our current work-around is to execute SVN.EXE Checkout as the first task in a job. This is problematic for a number of reasons. We cannot poll the repo for changes (same authenication problem when there are externals). Therefore, we have to use CRON based builds which really isn't continuous integration as we would like it to be. In addition we have to run additional custom tasks (CMake and/or Ant) to determine if the results of the build changed since the last build. We do this so we know whether or not to tag the code and whether or not to notify QA that a new build is available.
We would much rather use Repository polling because then we know a build runs only when a change did occur. We would always create tag (toss the customer scripts) and we could use Bamboo's built in notifications (if a build ran then a new release is available and toss those custom scripts also).
This is unfortunately a bug discovered in Bamboo 4.3.2:
It was not solved yet, as you can see. Please vote on it in order to increase its visibility and likelihood of being fixed faster.
As a project manager, I have discovered that different developers want to bring their previous branching method with them when they join the team. Some developers are used to performing individual wo...
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