# Surround SCM and branches

**URL:** <https://www.finalbuilder.com/forums/t/surround-scm-and-branches/5487>\
**Category:** Discussion\
**Created:** [June 15, 2016, 1:41am UTC](https://www.finalbuilder.com/forums/t/surround-scm-and-branches/5487 "2016-06-15T01:41:49Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![sindre](https://www.finalbuilder.com/forums/letter_avatar_proxy/v4/letter/s/48db29/32.png) [@sindre](https://www.finalbuilder.com/forums/u/sindre)\
**Post date:** [June 15, 2016, 1:41am UTC](https://www.finalbuilder.com/forums/t/surround-scm-and-branches/5487/1 "2016-06-15T01:41:49Z")

</div>

I don’t see any clear way to handle build on different branches with Surround SCM. It looks other repository types has some kind of Branch support at CI repository level.  
I don’t want to duplicate a configuration when I need to build for a specific branch.

---

<div class="post-metadata">

**Author:** ![Sparky](https://www.finalbuilder.com/forums/user_avatar/www.finalbuilder.com/sparky/32/10_2.png) [@Sparky](https://www.finalbuilder.com/forums/u/Sparky)\
**Post date:** [June 16, 2016, 1:27am UTC](https://www.finalbuilder.com/forums/t/surround-scm-and-branches/5487/2 "2016-06-16T01:27:06Z")

</div>

Hi Sindre,  
  
Unfortunately Continua CI only supports a single branch for Surround SCM repositories. We looked into supporting multiple branches, but found that Surround has a limitation which requires a separate workspace per branch.  
  
A workaround would be to use one Continua CI repository per Surround SCM&nbsp;branch, add each of these to the configuration and use a variable in the Repository Rules to the relevant repository to export on the agent.
