Search code examples
visual-studioazure-devopsrelease-managementcontinuous-deployment

Visual Studio Team Services: Release Management for layered infrastructure in an enviroment


I am trying to configure release management using VSTS (release hub). My Applications are distributed across several zones per environment. I have two different zones, each zone is considered a different network.

  • UI Applications will be on zone 1 (for this purpose I created Build Definitions "UI Build Definition" for UI Projects)

  • Service APIs on zone 2 (also created Different Build Definitions "ServiceAPI Build Definition)

Now, when new builds exits for each of them, I need to release each one to the corresponding Zone ( taking into consideration that the zones are different networks)

I am thinking that one agent will exist per zone to download the releases.

How to do the release management part? Configuration and specifying zones or servers per environment, link each release to a server in different zones?


Solution

  • I'm afraid there isn't any way to do this for now since you can only select one "Agent Queue" for one environment and there isn't any way to specify which Agent in the queue to use base on different networks.

    The alternative way for this would like what you think in the comments: Use two pipeline: Dev(Zone1)->QA(Zone1)->Prod(Zone1) and Dev(Zone2)->QA(Zone2)->Prod(Zone2). With this, you can specify different agents for different zones.