Perforce Check-out on Linux agent

Hi there,

I was testing upgrading our TeamCity server from version 8.0.6 to 9.1.1, and found out there are some differences in terms of checking out resources by using Perforce.
For example, I have a workspace in Perforce with a mapping like this:

//Depot/SourceCode/PythonCode/... //PYTHON_IMPLEMENTATION/...

Assume I have three files, test1.py, test2.py, test2.py in the workspace(in the directory of PythonCode).

By running the build with Perforce as VCS root, in 8.0.6, the working directory of the Linux build agent looks like this:

work/e4d42d13a9ec7153/PYTHON_IMPLEMENTATION/test1.py
work/e4d42d13a9ec7153/PYTHON_IMPLEMENTATION/test2.py
work/e4d42d13a9ec7153/PYTHON_IMPLEMENTATION/test3.py

But in 9.1.1, there is just a directory work/e4d42d13a9ec7153/. And the files are like:

work/e4d42d13a9ec7153/test1.py
work/e4d42d13a9ec7153/test2.py
work/e4d42d13a9ec7153/test3.py

Seems like the workspace name (PYTHON_IMPLEMENTATION) was skipped in the hierarchy of check out directory on build agent.

Is this a configuration issue in VCS root? Or is this a new feature that was introduced afterwards TC8.0.6?

Thanks!

1 comment
Comment actions Permalink

Hi Yang,

The behavior has not changed since 8.0.6. Please attach screenshot of the VCS root settings and teamcity-vcs.log file.

0

Please sign in to leave a comment.