VCS "load current repository state" for downstream builds?
Software versions:
Our project has 16 VCS roots. Why does TeamCity need to "load current repository state" for all 16 VCS roots before starting the "topmost" build (which has no dependencies and only 1 VCS root attached)?
- TeamCity Enterprise 8.1 EAP (build 29790)
- ClearCase 7.1.1
Our project has 16 VCS roots. Why does TeamCity need to "load current repository state" for all 16 VCS roots before starting the "topmost" build (which has no dependencies and only 1 VCS root attached)?
[19:12:41] Skip checking for changes - changes are already collected
[19:10:36] Will collect changes in 16 VCS roots
[19:10:36] Waiting for completion of current operations for all VCS roots
[19:10:38] Loading current repository state for VCS root 'VCS_Root1'
[19:11:22] Loading current repository state for VCS root 'VCS_Root2'
[19:11:23] Loading current repository state for VCS root 'VCS_Root3'
... (goes on for all 16 VCS Roots)
... (goes on for all 16 VCS Roots)
This causes our topmost build (with no dependencies) to wait over 2 minutes to start.
Thanks,
Bryan
Please sign in to leave a comment.