I have just updated a P4 client spec. to include several new client spec mappings but TeamCity (4.0.1 build 8171) does not pickup the changes (new 3rd Party jars for build). I checked that the mapping paths where correct and everything looked fine. However, after several build attempts (using the 'Clean all files before build') the new files where still not being mapped into the agent work dir.
I then decided to rename the client spec. and run a build. Strangely this worked as the new mapped files where synced down correctly. It looks like the original Perforce client spec state had been cached somewhere (TeamCity or p4d?). I have seen this "caching" behaviour with P4 client specs. before and the usual fix is to do a force sync (e.g. sync -f from cmd line).
Has anyone experienced this behaviour with P4 client specs. and TeamCity? Are there any workarounds that don't requrie a client spec. rename?