Integrate CI and CD together Azure Devops

Question

we need your support on enabling continues deployment on our release pipeline .

Environment : CI or Build Pipeline is on Azure Devops Services CD or Release pipeline is on Azure Devops Server

We want to Integrate CI and CD together right now after Build release is not kicking automatically.(I have to manually execute the release )

[![enter image description here][1]][1]

[![enter image description here][2]][2]

[![enter image description here][3]][3]

Service connection between azure devops service and azure devops server

[![enter image description here][4]][4]

# Trigger Release pipeline
- task: PowerShell@2
  displayName: 'Trigger Release pipeline'
  inputs:
    targetType: 'inline'
    powershell: |
     $url = "https://vsrm.dev.azure.com/{OrganizationName}/{ProjectName}/_apis/release/releases?api-version=6.0"
     
     $token = [System.Convert]::ToBase64String([System.Text.Encoding]::ASCII.GetBytes(":$($env:TOKEN)"))
     
     $JSON = @'
     {
       "definitionId": 38,
       "variables": {
            "Version": {
              "value": "$(build.buildnumber)"
            }
      
        }
     }
     '@
          
     $response = Invoke-RestMethod -Uri $url -Headers @{Authorization = "Basic $token"} -Method Post -ContentType application/json -body $JSON
    displayName: 'PowerShell Script'
    env:
      TOKEN: $(token)```


  [1]: https://i.stack.imgur.com/g4J8I.png
  [2]: https://i.stack.imgur.com/njsVU.png
  [3]: https://i.stack.imgur.com/MIaJJ.png
  [4]: https://i.stack.imgur.com/20wk9.png

Answer 1

We want to Integrate CI and CD together right now after Build release is not kicking automatically.

Since the azure devops service is on the cloud side and the azure devops server is local, there is no out-of-the-box feature that can Integrate CI/CD.

But you could use PowerShell task to run the Rest API in Azure Devops Service to trigger the Release on Azure Devops Server . Releases - Create

Here is an example:

You can add the Powershell Task to the end of the build, then you could add the following script in the powershell task:

$token = "PAT"

$url = "https://{instance}/{collection}/{project}/_apis/release/releases?api-version=5.0"

$token = [System.Convert]::ToBase64String([System.Text.Encoding]::ASCII.GetBytes(":$($token)"))

$JSON = @'
{
  "definitionId": DefinitionID(e.g. 15), 
  "description": "Creating Sample release",
  "artifacts": [],
  "isDraft": false,
  "reason": "none",
  "manualEnvironments": null
}
'@
     
$response = Invoke-RestMethod -Uri $url -Headers @{Authorization = "Basic $token"} -Method Post -ContentType application/json -body $JSON

If your CI/Build pipeline is running on self-hosted agent, you can directly add the powershell task at the same agent job.

If your build pipeline is running on Microsoft-hosted agent, you need to create a self-hosted agent and add additional agent job to run powershell script.

In this case, you also need to set the Dependencies.

Note: When running the rest api to trigger the azure devops server release, you need to ensure that they are in the same network range. So it needs self-hosted agent.

Update:

To define a stage, you could refer to the following doc and sample:

stages:
- stage: A
  jobs:
  - job: A1
    pool: 
     name: Default
    steps:
      - script: echo 


- stage: B
  pool:
    name: Default
  jobs:
  - job: B1
    steps:
       - task: PowerShell@2
         inputs:
           targetType: 'inline'
           script: |
             $token = "PAT"
             
             $url = "https://{instance}/{collection}/{project}/_apis/release/releases?api-version=5.0"
             
             $token = [System.Convert]::ToBase64String([System.Text.Encoding]::ASCII.GetBytes(":$($token)"))
             
             $JSON = @'
             {
                "definitionId": ID,
               "variables": {
                    "Version": {
                      "value": "$(Build.buildnumber)"
                    }
              
                }
             }
             '@
                  
             $response = Invoke-RestMethod -Uri $url -Headers @{Authorization = "Basic $token"} -Method Post -ContentType application/json -body $JSON

Update2：

In order to achieve a function similar to the system.accesstoken variable, you can try the following settings.

Step1: Create a variable in Azure Devops Service Build Pipeline and set it as variable:

Step2: PowerShell Task script:

- powershell: |
   
   
   $url = "https://{instance}/{collection}/{project}/_apis/release/releases?api-version=5.0"
   
   $token = [System.Convert]::ToBase64String([System.Text.Encoding]::ASCII.GetBytes(":$($env:TOKEN)"))
   
   $JSON = @'
   {
     "definitionId": 38,
     "variables": {
          "Version": {
            "value": "$(build.buildnumber)"
          }
    
      }
   }
   '@
        
   $response = Invoke-RestMethod -Uri $url -Headers @{Authorization = "Basic $token"} -Method Post -ContentType application/json -body $JSON
  displayName: 'PowerShell Script'
  env:
    TOKEN: $(token)