VCS Build Triggering Issues

I'm having problems getting the VCS builder triggers to work correctly. I am using perforce as my VCS and I have read the documentation, http://www.jetbrains.net/confluence/display/TCD4/Configuring+VCS+Triggersbut I can't get it to work correctly.

I have tried:

-://depot/branches/**
-:/depot/branches/**
-:depot/branches/**

-://client/branches/**
-:/client/branches/**
-:client/branches/**

-://client mapping/branches/**
-:/client mapping/branches/**
-:client mapping/branches/**

-://branches/**
-:/branches/**
-:branches/**
-:/**/branches/**
-:**/branches/**

Can someone please help?
Do I need to stop and re-start team city for the changes to take effect?
Has anyone successfully used VCS build triggering with perforce?

1 comment
Comment actions Permalink

I use a custom client mapping to only check out folders I need for building and testing.

For example, if your custom client mapping is...
//depot/branches/main/... //team-city-agent/branches/main/...

The TeamCity workspace is rooted at //team-city-agent so make sure your triggers use a relative path from that point.

//team-city-agent/branches/main/
folder1
folder2
folder3
file1
file2

To not trigger on changes made inside the folder2 folder you would set your ignore pattern to
-:branches/main/folder2/**

Remember that TeamCity will see the changes in the folder, and it will report Pending changes for the build, but it just won't trigger the build until something outside of folder2 changes. This can be useful for XML files, or *.properties files that aren't worth a full build, or would not affect the compilation and tests, but are required in the build artifacts.

0

Please sign in to leave a comment.