TC and mixed VCS module branches how to

TC 5433, agent/server running on RHEL3

This may be a dumb thing to ask, but how do you configure a project which uses
CVS repository modules which involve different branches?

we have a setup where some modules (that are common across projects/apps)
are of a particular branch or version tag and others which are specific to the current
project may be at different stages of development so they have their own tags, i.e.:

commonModule1 -> VER_1_1_0
commonModule2 -> VER_1_1_0
appModule1-> VER_1_5_0
appModule2-> HEAD

with IDEA, we simply set up the project to check the appropriate modules either
as source or as build artifacts (jars) with the appropriate tag, furthermore, each such
module is a directory under some application development root and there is a
build file that orchestrates all the necessary activities.

I'm having a real hard time defining this structure in TC as far as the VCS settings
are concerned - if I specify multiple VCS roots, as soon as the checkout of the first
root is complete, the begining of the second root definition causes the files to be
If I specify a directory (corresponding to a module) with a particular branch, I get the contents of the firectory checked out onto the root build directory. If I specify
a mapping rule that maps the directory to some other directory it does not end
up in the right place (This may be my misunderstanding of the mapping, but I am not sure what the relationship between the module name and the VCSPath as the
source in a mapping rule is).

If I use a CVS modules file, I get all kinds of strange results, depending on what
type of module I actually use (alias, &, directory).

This makes it really difficult for me to try and sell the idea of TC in our environment,
especially since all the checkout functionality works out of the box with the CVS
client, and with our build tools.

Can someone shed some light on this?



1 comment
Comment actions Permalink

The question perhaps no longer relevant. If it's not please leave a comment or create a separate thread.

Kind regards,

Please sign in to leave a comment.