We've been testing out TeamCity Professional Edition for our build process and can't seem to get it to reliably pickup changes for SVN repositories with svn:externals.
We are using Subversion for our repositories and have that working well. Using a client like Tortoise SVN we can update/commit with no problems.
We have say around 12 repositories. Some are utilities, tools and documentation that get incorporated into other repositories as svn:externals.
Here a simplified model of what our repository looks like
Our Documentation Project
[Repository 'OurProduct_Build'] <- This build does not pick up changes in any of the externals
-> svn:external: 'OurProduct_Trunk'
-> svn:external: 'OurProduct_Docs'
OurBuildScript.ps1 <- This is our build script which compiles everything together from multiple externals into one final set of deliverables, works fine
So the 'OurProduct_Build' repository is what puts the whole product together software, documentation, etc... and therefor contains some build scripts and externals to 5 or 6 other repositories that include our tools/utilities, documentation, and product trunk source. The build scripts will end up using resources from each of these externals when producing the build artifacts. The build process works great and all externals are used correctly; however, any changes committed to one of these externals do not reliably get picked up by TeamCity prompting a pending build. So we don't see the "Pending" changes on the main "overview" page of TeamCity for this build. However, the changes are reflected for projects pointing directly to 'OurProduct_Trunk' which of course has no externals.
Am I doing something fundamentally wrong with the VCS setup here, or is this a bug in TeamCity not checking externals?
Our Repository is set for 'Default config Directory = true' and 'Externals Support = Full Support'. The build VCS config is set to checkout "automatically on server".
Any help or tips are appreciated!