Command Line Remote Runner

1) How many projects/builds can be in one .teamcity-mappings.properties file?

2) Is there a way to create mappings.properties files for all the projects in my system?

3) Looking at the contents of a mappings file, how can I tell which build type it mapps to?  For example, I have a "teamcity-mappings.properties" file with this content:

.=svn://ef12b8d8-8b0c-40c8-b26f-aba45b024271|trunk/stafTests

../dbFiles=svn://ef12b8d8-8b0c-40c8-b26f-aba45b024271|trunk/dbFiles

../Apex=svn://ef12b8d8-8b0c-40c8-b26f-aba45b024271|trunk/n4-app/apex/etc/dev

../Tools=svn://e0df03b8-ab0a-43f7-a400-cebd430cd4d0|branches/carina_6_0_A-rel/framework/tools



Is it easy to tell what build it is for?

Thanks.
-T
1 comment
Comment actions Permalink

teamcity-mappings.properties does not have any information about build configurations intentionally. It stores VCS specific information which allows TeamCity server to check whether build configuration specified in command line is compatible with patch created by command line tool.
With this approach if you create new build configuration with same VCS settings there is no need to regenerate mapping file.

However, I agree that the whole usability of the tool is low, this is the main reason why we do not bundle it. For example, it could have a command to list all build configurations that can be triggered using specified mapping file. I think this would solve your problem.

0

Please sign in to leave a comment.