Is it possible to trigger a build config on VCS changes outside the VCS root?
Context: One of our build configs invokes an external testing system. Thus, the build config
* only needs very little code (some infrastructure to invoke the external testing system), so ideally it should only have a tiny VCS root
* has to monitor (trigger on) changes to a huge VCS area (25 GB).
Right now, the build config is syncing the whole VCS area (25 GB) but as explained above, it doesn't use it at all. (The external testing system is also syncing that VCS area and actually uses it.)