Perforce VCS Root - Unrelated changelist used for check out

Completed

Hi,

On our TeamCity (2019.1.4 build 66526), running on Linux, we are observing a behavior that is not right.

First, let's mention that in the same perforce server, we have several depots, all being alive :

//my/dev/main

//ty/dev/main

//sy/dev/main

We have create a VCS Roots for Perforce and we use a P4 Client mapping to configure what to sync :

//my/dev/main/... //team-city-agent/my/main/...

We don't use branch filtering at any point.

Now, when we run a build, the changelist used to sync may come from totally different repository! Like from //ty/dev/main instead of //my/dev/main

The setup is simple and straightforward, but it seems we are doing something wrong.

We went through the doc, but don't find any answer.

Does this behavior rings a bell?

Thank you in advance for your help.

0
1 comment

For reference of anybody reading this, it has been handled in our issue tracker: https://youtrack.jetbrains.com/issue/TW-63725 . Please check it out.

0

Please sign in to leave a comment.