Thanks Marek. Unfortunately we're split between Perforce, SVN, and Git, with Git being heavily in the minority. While Git and Plan Branches are compelling features, a full transition isn't in our near future given our current release/branching strategy, so we'd definitely need the feature built into Bamboo proper to utilize it.

thomas.vanbuskirk
Feature branches could be alternative approach.
If you are using git or hg, it is nice alternative.

What repository are you using?

My company would move from TeamCity to Bamboo if this feature were included. We've become quite reliant on the pre-commit build execution as part of our flow, and it is heavily ingrained into our processes. If there's any alternate way of getting similar behavior in Bamboo (outside of this feature being implemented) or other workaround I'd be very interested.

My company is also very interested in this feature. We have several very large projects stuck in Subversion, which cannot be moved to git. Moreover, the Plan branches don't work for the teams as they continuously check in their code into the mainline. We absolutely want this feature in Bamboo.

In my company's case, we need to use a customized repository plugin to detect changes and check out code. And while we can set up branches manually, it would be nice if the repository plugin API provided hooks for automatic branching that we could implement.

You will need to implement these interfaces to support branch detection on your custom repository type. A good example on how todo so is the Bamboo Git Plugin.

http://docs.atlassian.com/atlassian-bamboo/latest/com/atlassian/bamboo/repository/BranchAwareRepository.html
http://docs.atlassian.com/atlassian-bamboo/latest/com/atlassian/bamboo/repository/BranchingAwareRepository.html

I'd like to hear why using Plan Branches as Personal Builds doesn't work for you particularly now that almost half of teams we talk to today are using Git in some form and more are considering switching.

The Plan Branches is a step in the right direction. But if "almost half" the teams are using or moving to Git, then that means that more than half your customers aren't using Git. In my company's case, we need to use a customized repository plugin to detect changes and check out code. And while we can set up branches manually, it would be nice if the repository plugin API provided hooks for automatic branching that we could implement.

Hi there,

I believe that the value of introducing a personal builds feature has diminished with the rise of Git/Mercurial, the practice of Feature Branching and Bamboo's introduction of Plan Branches.

When Bamboo detects a branch in Git, Mercurial or Subversion it automatically detects creator of the branch and reports it on the summary for that branch.

I'd like to hear why using Plan Branches as Personal Builds doesn't work for you particularly now that almost half of teams we talk to today are using Git in some form and more are considering switching.

Thanks,
James Dumay
Product Manager

Come on Atlassian! Pull your finger out. This is a BIG feature miss compared to other CI servers.

Pull requests would be a nice addition to patches.