How can we improve Azure DevOps?

Allow TFS build to depend on multiple repositories

This suggestion is migrated to Developer Community. Please use below link to view the current status.
https://developercommunity.visualstudio.com/content/idea/365522/allow-tfs-build-to-depend-on-multiple-repositories.html
Many other build systems allow dependencies on multiple source repositories ( even different ones - i.e. Git and SVN).

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.

423 votes
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Jason shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    26 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      Submitting...
      • Anonymous commented  ·   ·  Flag as inappropriate

        This is to the poster who asked if this was an Anti-Pattern. Not at all!!!

        Consider a Microservice based solution where each service/app followed the tenants of the Twelve Factor App. The 12 suggests that each app has it's own repo. In order to perform an entire system build you would be required to pull in many different repos.

        Now, you can probably accomplish this with git sub-modules, but IMHO I feel like the build should support multiple repos. So +1 here too!

      • Taylor Mansfield commented  ·   ·  Flag as inappropriate

        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.

      • Brian Thomason commented  ·   ·  Flag as inappropriate

        This is something my company needs as well, we have our Website in it's own repo, and the models/services is uses in others that are a mixture of TFVC AND VSTS Git repos.

      • Anonymous commented  ·   ·  Flag as inappropriate

        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.

      • Forrest Trepte commented  ·   ·  Flag as inappropriate

        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!

      ← Previous 1

      Feedback and Knowledge Base