Work around for not being able to apply checkout rules to single files?


Our existing codebase is stored in CVS using a structure of one master project root and master build file that build selected subprojects.
Each build will checkout different subprojects but always need the master build files.

Looks Like:
- build.xml
- subproject1\
- subproject2\
- subproject50\

Currently we have a separate root setup for each subproject.  Some builds have as many at 30 roots. This can be difficult to maintain.

What I would like to do is have a single VCS Root with a checkout rule that only brings in the modules that I need including the single file.

From what I have read, this is not possible. Has anyone found a work around for this?
We are using 6.5.3 and are planning to upgrade to 7.x soon.
Is there a planned feature for this?

Any help would be appreciated.


1 comment
Comment actions Permalink


The only workaround for checking out a single file I can juggest is: exclude all the directories in the checkout rules, then delete/move the files as a first build step to produce necessary file structure in the checkout directory.

Also, you can try to checkout the file inside the build script using the VCS revision passed by TeamCity into the build.
Related issues in the tracker: TW-8415, TW-3460.


Please sign in to leave a comment.