Perforce RCS keyword expansion

Has anyone seen issues with stale RCS keyword values when checking out files from Perforce?


In particular, we have a build that stores the current changelist number in a file with the "text+k" filetype. Inside the file there is a $Change:$ keyword. However, the changelist number in the checked-out file is often several revisions behind the %build.vcs.number% that TeamCity reports.


I'm using server-side checkout with the "Clean all files in the checkout directory before the build" option enabled.


Is this a known issue? Is there some configuration that I can use to keep these in sync?


 

0
1 comment

Please try using agent side checkout.

0

Please sign in to leave a comment.