Purpose of multiple VCS roots?

Hello,

  Is the purpose of multiple VCS roots solely to merge source together prior to a build?  I'd like to share a build configuration for a module across the trunk and multiple branches if possible.  It doesn't seem like using multiple VCS roots is appropriate for this need.  Do I need to copy the build configuration for each branch as they are created?  I'd like to keep the configurations down so I don't duplicate the configuration (and have to update a lot of configs if I ever need to update something).

Thanks,

  Chris Schmidt

4 comments

That is how we are using the multiple VCS root capability.

0

  Are you using checkout rules to keep the branches apart?  If so, how do you get the configuration to build in the different directories?

  For example, if I have two VCS roots defined with checkout rules to put the information into -> /trunk and /branch1, how does the build runner configuration run in both locations?  do you manually change the build runner's configuration to point to every branch's directory?  Ideally, I'd like it to check out one VCS and build, then the next if needed.  That way the build configuration doesn't need to change at all.  The only variance is the set of VCS roots that I've currently attached to it.

Thanks,

  Chris

0

do you manually change the build runner's configuration to point to every branch's directory

That's exactly what we do here.
Usually you don't too many branches... :

  • baseline (for production hotfix)
  • nextrelease (trunk or some branch depending on how you work)
  • projectA that spans multiple releases
  • projectB that spans multiple releases


So we duplicate around project & their build configuration.

Gilles

0

  Thanks for the information.  In my company's case, we have a lot of modules shared across product teams.  Each product team, in some cases, needs to branch one or more core modules.  It would be nice to have a single configuration in cases like this because I can see us having a large number of configurations for the core modules...  We'll be able to get through it.  This is more of a feature request anyway.

Thanks!

  Chris Schmidt

0

Please sign in to leave a comment.