title: VSTS: Release Management Binding Release Definition to Multiple Builds or Projects
body: <p>I am trying to configure release management using VSTS (release hub).  I have three different environments; each environment contains two servers.</p>
  
  <p>The Proposed Release pipeline:</p>
  
  <p>Zone1_Dev -> Zone1_QA ->Zone1_PROD  (where each one contains two severs)</p>
  
  <p>Talking about the "Zone1_Dev" Environment which contains two servers A and B in the same network.</p>
  
  <p>I have two web applications in my solution, Each Server will host different application:</p>
  
  <ul>
  <li>Server A hosts the Client UI (MyClientUI)</li>
  <li>Server B hosts the Admin UI (MyAdminUI)</li>
  </ul>
  
  <p><a href="https://i.stack.imgur.com/hB95R.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/hB95R.png" alt="enter image description here"></a></p>
  
  <p>So, I created two different Build definitions one for each of the applications, because I want to avoid building the two projects (because they don’t affect each other).</p>
  
  <p><a href="https://i.stack.imgur.com/70sQc.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/70sQc.png" alt="enter image description here"></a></p>
  
  <p>AdminUI definition mapping to MyAdminUI Project:</p>
  
  <p><a href="https://i.stack.imgur.com/3lQBZ.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/3lQBZ.png" alt="enter image description here"></a></p>
  
  <p>Then, I Created One Release definition, Because I will move through the release pipeline as following:
     Zone1_Dev -> Zone1_QA ->Zone1_PROD</p>
  
  <p><a href="https://i.stack.imgur.com/Dft5D.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/Dft5D.png" alt="enter image description here"></a></p>
  
  <p>The agent is installed on Server A, which will get any of the changes, either in AdminUI or ClientUI. If it is: </p>
  
  <ul>
  <li>ClientUI, it will move it to Sever A IIS directory.</li>
  <li>If AdminUI, the agent will move it to Server B IIS directory.</li>
  </ul>
  
  <p>My Problem, how I can link one release to different build definitions.  Because according to my strategy, I have to create two different release definitions with the same configuration but different build definitions. Is there is a way to do that in one release definition since they share the same pipeline?</p>