如何在部署新版本之前检查以前版本是否已完成 [英] How to check if a previous release has been completed before deploying a new release

查看:18
本文介绍了如何在部署新版本之前检查以前版本是否已完成的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

作为发布管道的一部分,我们有一个任务(最后一个任务)将发布分支合并回主分支。

我想知道是否有办法在允许新版本排队之前检查此任务或上一个版本是否已完成。可以为此使用闸门吗?

理想情况下,发布经理将能够决定是继续发布还是取消发布。

推荐答案

您不能将Invoke睡觉API入口与Azure DevOps API url一起使用,因为要检查上次发布状态,您需要检查环境(Stage)状态,为此,您需要提供版本id(这样您就无法知道它会是什么,并将其放入睡觉API入口URL中)。

但是,您可以使用PowerShell检查最新版本,如果没有成功,则阶段失败。

在您的版本中添加PowerShell任务以检查最新版本:

$headers = @{ Authorization = "Bearer $env:SYSTEM_ACCESSTOKEN"  }

# Replace {org} with your organization
# Replace {project} with your project
# Replace {defId} with your release definition id

$url = "https://vsrm.dev.azure.com/{org}/{project}/_apis/release/releases?definitionId={defId}&api-version=5.1"
$releases = Invoke-RestMethod -Method Get -Uri $url -Headers $headers -ContentType 'application/json'

$releaseUrl = "https://vsrm.dev.azure.com/{org}/{project}/_apis/release/releases/$($releases.value[1].id)?api-version=5.1"
$releaseInfo = Invoke-RestMethod -Method Get -Uri $releaseUrl -Headers $headers -ContentType 'application/json'

$releaseEvnriomentId =  $releaseInfo.environments.Where({ $_.name -eq 'THE STAGE NAME WHERE YOU DO MERGE' }).id

$envUrl = "https://vsrm.dev.azure.com/{org}/{project}/_apis/Release/releases/$($releases.value[1].id)/environments/$($releaseEvnriomentId)?api-version=5.1-preview.1"
$environment = Invoke-RestMethod -Method Get -Uri $envUrl -Headers $headers -ContentType 'application/json'

$envStatus = $environment.status

if($envStatus -ne "succeeded")
{
    Write-Error "Previous release not succeeded!"
}
else
{
    Write-Host "Previous release succeeded :)" 
}

在代理作业选项中,您需要允许脚本访问OAuth内标识:

Azure函数也支持PowerShell,因此您也可以使用Azure函数GATE:

1)使用VS代码创建新的Azure函数,如here所述。

2)在run.ps1文件中将代码替换为此代码:

using namespace System.Net

# Input bindings are passed in via param block.
param($Request, $TriggerMetadata)

# Write to the Azure Functions log stream.
Write-Host "PowerShell HTTP trigger function processed a request."

$defnitionId = $Request.Query.DefinitionId

# Generate PAT and put it in the {YOUR PAT}
$base64AuthInfo = [Convert]::ToBase64String([Text.Encoding]::ASCII.GetBytes(("{0}:{1}" -f $user,"{YOUR PAT}")))
$headers = @{Authorization=("Basic {0}" -f $base64AuthInfo)}

# Replace {org} with your organization
# Replace {project} with your project

$url = "https://vsrm.dev.azure.com/{org}/{project}/_apis/release/releases?definitionId=$($defnitionId)&api-version=5.1"
$releases = Invoke-RestMethod -Method Get -Uri $url -Headers $headers -ContentType 'application/json'
Write-Debug $releases

$releaseUrl = "https://vsrm.dev.azure.com/{org}/{project}/_apis/release/releases/$($releases.value[1].id)?api-version=5.1"
$releaseInfo = Invoke-RestMethod -Method Get -Uri $releaseUrl -Headers $headers -ContentType 'application/json'
Write-Debug $releaseInfo

$releaseEvnriomentId =  $releaseInfo.environments.Where({ $_.name -eq 'THE STAGE NAME WHERE YOU DO MERGE' }).id

$envUrl = "https://vsrm.dev.azure.com/{org}/{project}/_apis/Release/releases/$($releases.value[1].id)/environments/$($releaseEvnriomentId)?api-version=5.1-preview.1"
$environment = Invoke-RestMethod -Method Get -Uri $envUrl -Headers $headers -ContentType 'application/json'
Write-Debug $environment

$envStatus = $environment.status
Write-Debug $envStatus

if($envStatus -ne "succeeded")
{
    $status = [HttpStatusCode]::BadRequest
    $body = "failed"
}
else
{
    $status = [HttpStatusCode]::OK
    $body = "success"
}


# Associate values to output bindings by calling 'Push-OutputBinding'.
Push-OutputBinding -Name Response -Value ([HttpResponseContext]@{
    StatusCode = $status
    Body = $body
})

3)将函数发布到Azure。

4)在您的版本中创建调用Azure函数入口:

另一种选择,获取上面的代码,将其转换为C#或其他语言,然后使用睡觉应用编程接口,部署到它的Web服务器,然后使用调用睡觉应用编程接口网关。

这篇关于如何在部署新版本之前检查以前版本是否已完成的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆