I'm using TeamCity 9.0.2 with agent-side Perforce checkout. I have a build config template where a VCS root has p4 mappings specified in TC. TC then creates a p4 client during the build and syncs code to the checkout directory. The build shows the client name and the checkout directory. It seems like the client name follows this pattern:
TC_p4_[agent name]_[build config name]_92275c20adc9d046
The default checkout directory is something like this:
[agent work directory]/1d27c2beb4cf17e1
How are both alpha-numeric patterns at the end generated?
Are there controls that can influence those patterns?
I am asking because I am using a build config template with many derived build configs, and the checkout directory is reused between those builds. I haven't had a chance to test what happens if these builds run on the same machine. Does checkout directory get reused? Cleaned?
I have seen those alpha-numeric patterns change if I change the mapping in the VCS root, but perhaps there are other ways to control it. I realize that a workaround is to use a custom path for checkout directory setting like %teamcity.build.default.checkoutDir%\MyBuildConfigName, but I'm hoping there are other, better ways for this.