title: Control Job Order in Azure DevOps Release Pipeline
body: <p>I have a complicated release that spans multiple deployment groups and I am planning to use the 3rd party <a href="https://github.com/jabbera/vsts-git-release-tag" rel="noreferrer">vsts-git-release-tag</a> extension to tag the release. Ideally, the entire release (all jobs) would succeed first before tagging the repository.</p>
  <p>So I am trying to work out what the best way to accomplish that is. If this were a build pipeline rather than a deployment pipeline, it is clear I could just arrange them <a href="https://docs.microsoft.com/en-us/azure/devops/pipelines/process/multiple-phases?view=azure-devops&amp;tabs=yaml" rel="noreferrer">using <code>dependsOn</code></a>, as follows.</p>
  <pre><code>jobs:
  - job: Deployment_Group_1
    steps:
    - script: echo hello from Deployment Group 1
  - job: Deployment_Group_2
    steps:
    - script: echo hello from Deployment Group 2
  - job: Tag_Repo
    steps:
    - script: echo this is where I would tag the Repo
    dependsOn:
    - Deployment_Group_1
    - Deployment_Group_2
  </code></pre>
  <p>However, there doesn't seem to be equivalent functionality (at least currently) in release pipelines as specified <a href="https://docs.microsoft.com/en-us/azure/devops/pipelines/process/multiple-phases?view=azure-devops&amp;tabs=yaml" rel="noreferrer">in this document</a>.</p>
  <blockquote>
  <h2>Note</h2>
  <p>Running multiple jobs in parallel is supported only in build pipelines at present. It is not yet supported in release pipelines.</p>
  </blockquote>
  <p>Although it doesn't specifically mention the <code>dependsOn</code> feature, there doesn't seem to be a way to utilize it in release pipelines (correct me if I am wrong).</p>
  <p>I realize I could probably create a separate stage containing a single job and task to create the Git tag, but that feels like a hack. <strong>Is there a better way to run a specific release job after all other release jobs have completed?</strong></p>