We use TeamCity as our CI server, and are very happy with it. I'm trying to integrate a home-grown tracking system that we use for, among other things, specifying SQL dependencies and apply order for builds. The tracking system stores everything in MSSQL 2k, while version control is in PVCS. Moving away from PVCS for these files is not an option at the moment.
I have written a vbscript that does a few things, etc etc, gets a list of files, and processes them. It runs fine from the command line. When run from the TeamCity Command Line Runner, it fails.
I use two PVCS command line tools, vcs.exe to apply a promotion group, and pcli.exe to get the file, and apply a version label. vcs.exe returns error code 1, pcli returns error code 3.
Teamcity service and agent both run as 'teamcity', a domain user account.
v:\pvcs is mapped to the repository. teamcity user has been given full control
d:\build is a temp directory. teamcity user has been given full control
The PVCS client runs and works fine - sees the repository no problem.
PVCS command line tools are in the path and can be run no problem. Looking at the agent environment in TeamCity, the path lists them there as well.
The code box lists some log output from team city. When something fails, I output the cmdline that was trying to run. I can copy and paste that and it will run successfully.
[11:23:29]: [AdminMiscellaneous.html] runCmd
[11:23:29]: [AdminMiscellaneous.html] Failure: Couldn't apply TEST promotion group. Code: 1; Command: vcs -cV:\PVCS\archives\ctpkppx1.cfg -#3 -Y -gTEST:1.6 v:\pvcs\archives\com\docs\html\AdminMiscellaneous.html
[11:23:31]: [AdminMiscellaneous.html] runCmd
[11:23:31]: [runCmd] 11:23:31 Feb.23.09 [Error]
[11:23:31]: [runCmd] The project root could not be loaded: "v:\PVCS".
[11:23:31]: [AdminMiscellaneous.html] Failure: Couldn't get AdminMiscellaneous.html. Code: -3; Command: pcli run -y get -prv:\PVCS -nm -ad:\build\pvcs -o -bp/ -r1.6 /com/docs/html/AdminMiscellaneous.html