VCS checkout rules with Perforce agent-side checkout

Hi all,

I'm trying to replicate the setup described here, with Perforce agent-side checkout: http://devnet.jetbrains.net/message/5284510

The setup I'd like to achieve is to define one VCS root that's shared between all projects. Each project should define VCS checkout rules according to the directories it needs. I can make it work fine with server-side checkout: I add a VCS root with a client mapping set up so that most of the depot is included, then I add projects with more specific checkout rules. However I can't get TeamCity agents to generate the correct Perforce client mapping.

Given a VCS root like this:

//depot/main/src/... //team-city-agent/src/...

...I can make the agent work with a checkout rule like this:

+:src

But given the same VCS root, and more specific checkout rules like this:

+:src/projectA

+:src/projectB

+:src/projectC

...I get a blank Perforce client spec generated on the agent machine, and the build fails with a "file(s) not in client view" error.

It's as if TeamCity is looking for an exact match between the project's checkout rule and the right-hand side of the VCS root's client mapping. Apparently the poster at http://devnet.jetbrains.net/message/5284510 made it work OK, but I can't see what I'm doing wrong.

(This is on TeamCity 7.0.2. Server is Linux, agents are Windows. The Perforce version is 2011.1.)

Thanks,

Tim

2 comments
Comment actions Permalink

Hello Tim,

   It is possible that there is some problem with client mapping generation logic. To find out, whether this is the case, I need more details about the setup.

   Specifically, I need information about your depot structure, how client mapping specification looks like for your VCS root, and which client mapping you're trying to use.

   Also, I'd ask to enable Log4j debug logging on build agent for category jetbrains.buildServer.VCS.P4 and attach VCS debug logs from build agent for your case.

   Probable, it worth creating an issue in our issue tracker to collect all this information (and you can restrict access to sensible information in the issue tracker).

   Thanks!
   KIR

0
Comment actions Permalink

Thanks Kirill. I've raised

http://youtrack.jetbrains.com/issue/TW-22494, and attached log files and configuration details.
0

Please sign in to leave a comment.