VCS trigger rules with perforce sparse branches

Hi all,

I have a question regarding VCS trigger rules for sparse branches in perforce.

I have a project with the following VCS mapping in perforce

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

+//depot/private/my_branch/... //team-city-agent/...

The "+" sign signifies that my_branch is a sparse branch.

Now, I want to setup a VCS trigger, which triggers a build whenever there is change on my_branch, but does not trigger a build for changes on the underlying "main".

I tried

+://depot/private/my_branch/**

But it doesn't work (triggers no builds at all).

What is the correct VCS trigger mask in this case?

Thanks

1 comment
Comment actions Permalink

Anyone knows the answer or some similar solution?

0

Please sign in to leave a comment.