Trigger by change in Folder rather than by Repository.
Answered
I'm evaluating TeamCity with .NET for the first time and would like to know if I can do the following:
1- Trigger build/actions by a change in file or folder (It won't be building source, just triggering actions when the source exe changes)
2- Copy changes to a test sandbox
3- Execute tests in sandbox.
I have done all of these previously using Jenkins, but would like to migrate to TeamCity. If you can refer me to a sample link instead, it would be great.
Please sign in to leave a comment.
Hi there,
Points 2 and 3 are simple. Copying the changes and running tests in a sandbox is basically how TeamCity works by default (copies the VCS contents to a work folder on the build agent, runs a set of build steps in that work folder). If you want to use a specific sandbox, it can also be set up.
Point 1 depends on how your environment is set up. If the file (or folder) is in a VCS system (no need for it to hold source code, it only needs to be in a VCS) then it would be possible. You can also trigger a personal build using an IDE (Remote run), or simply commit the file to the VCS, and TeamCity will trigger automatically if you have set up a VCS Trigger. If the file/folder is not on a VCS, it's currently not possible.
Git is usually very easy to configure to work in this way, as the "repository" is just a folder. You would just need to run the "git commit" command on the files/folder after the changes for TeamCity to pick it up.