Answers: <p>Do not trigger Build 2 automatically from Build 1. Instead add a last step to Release 1 to queue Build 2. There are a few ways to do it, e.g. <a href="https://stackoverflow.com/questions/52821204/how-to-queue-build-pipeline-as-task-from-release-pipeline">https://stackoverflow.com/questions/52821204/how-to-queue-build-pipeline-as-task-from-release-pipeline</a></p>
  
Answers: CC BY-SA 4.0
Answers: 2019-02-26T20:53:00.457Z
Answers: 2019-02-26T20:53:00.457Z
Answers: Giulio Vian
Body: <p>I have this setup:</p>
  
  <ol>
  <li>Build 1 builds and trigger Release 1 when finished</li>
  <li>Build 2 is triggered by Build 1 and release Release 2</li>
  </ol>
  
  <p>If I have one parallel job, can I be sure that:</p>
  
  <ul>
  <li>Release 1 is always run before the Build 2 is triggered?</li>
  </ul>
  
  <p>I have tested this, and it does the above, but I can't find any documentation on the flow anywhere.</p>
  
  <p>I need to release Release 1 before build 2 starts.</p>
  
Tags: <azure-devops><build-pipeline><release-management>
Title: Microsoft DevOps: build triggering vs release
UserDisplayName: mslot
ThreadText: # Microsoft DevOps: build triggering vs release
  
  (Asked by: username_0 on 2019-02-25)
  
  I have this setup:
  
  1. Build 1 builds and trigger Release 1 when finished
  2. Build 2 is triggered by Build 1 and release Release 2
  
  If I have one parallel job, can I be sure that:
  
  * Release 1 is always run before the Build 2 is triggered?
  
  I have tested this, and it does the above, but I can't find any documentation on the flow anywhere.
  
  I need to release Release 1 before build 2 starts.
  
  **Tags:** azure-devops, build-pipeline, release-management
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2019-02-26. Score: 1 | Accepted answer
  
  Do not trigger Build 2 automatically from Build 1. Instead add a last step to Release 1 to queue Build 2. There are a few ways to do it, e.g. <https://stackoverflow.com/questions/52821204/how-to-queue-build-pipeline-as-task-from-release-pipeline>
  
  
  ---
  
  