I currently have setup a TFS project that has multple Git repos and TFS source repositories. I have builds that depend on a mixture - for instance a main build has a dependency on a Git repo that contains 3rd party dependencies. While there is a work around with the general command line support, it would be much more clear to define the source dependencies up front. I should be able to specify the branches on those via variables also. I know that TeamCity supports multiple source control repos. Take a look at that implementation.

Isn't this something of an anti-pattern? If a build depends on several repos, isn't it impossible to reproduce any builds outside of TFS without a priori knowledge? For example, if I have a test library repo that gets built with a app repo, how would my developers ever be able to successfully run tests locally without knowing beforehand that you need both repos? Not to mention that you decouple the version of the tests from the version of the app. That makes it entirely inauditable. A solution to this is to use the test repo as a submodule to the app repo, but submodules come with their own set of problems.

The feature should also be added for VSTS. When multiple repos can be specified for the same build, it will be quite convenient that one CI Build definition for multiple repos instead clone multiple CI build definitions for each repo separately.

My team has some custom build processes that we run a combination of multiple internal team repositories and external open-source repositories. Currently we have to have a single master repository with build scripts to manually clone the other repositories every time. If VSTS could support multiple repositories in the Get Sources part of the build definition it would save us a lot of complexity!

Now that TFS/VSTS allows for multiple repositories in a single Team Project, this is a much needed feature. I work as consultant in the DevOps space to recommend tools and help companies manage their SDLC's and mature their process. Recently on this topic I've gotten a lot of strange looks when I tell clients how they have to manage multiple repositories in a single build with TFS/VSTS. This should be easy for the end-users and built directly in the tool without the need for script hacking and/or git manipulations.