使用AWS CodePipeline中的多个版本进行手动审批 [英] Working with manual approvals for multiple builds in AWS CodePipeline

查看:86
本文介绍了使用AWS CodePipeline中的多个版本进行手动审批的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我们设置了CodePipeline,以进行构建,部署到QA ECS环境,然后手动批准步骤以部署到Prod.

We have a CodePipeline set up to do a build, deploy to a QA ECS environment, then a manual approval step to deploy to Prod.

然而,令人困惑的是,当有多个构建相继运行时.几个构建已按顺序部署到质量检查中,但是批准"按钮似乎一次批准了一个构建,因此,当您单击时,尚不清楚要批准哪个构建.

What gets confusing though, is when there are several builds running one after another. Several builds get deployed to QA in sequence, but then the Approval button seems to approve them one at a time, and it's not clear which build you're approving when you click on it.

我想做的是批准最新的版本,以防万一 较早的版本具有后来的版本所修复的问题.最好的方法是什么?

What I would like to be able to do is to approve the latest build, in case the earlier builds had issues that were fixed by the later builds. What would be the best way to accomplish that?

推荐答案

您应将部署和批准操作置于同一阶段.这使您可以完全批准所测试的内容.为什么?因为在任何给定时间,只有一个管道执行可以处于管道阶段.

You should place the deploy and approval action in the same stage. This lets you approve exactly what you tested. Why? Because exactly one pipeline execution can be in a pipeline stage at any given time.

...批准最新版本,以防早期版本出现问题 在以后的版本中已修复.

...approve the latest build, in case the earlier builds had issues that were fixed by the later builds.

如果您希望以后的版本赶上来,请拒绝等待批准的早期版本.

If you want to let later builds catch up, reject the earlier build that is waiting for approval.

这篇关于使用AWS CodePipeline中的多个版本进行手动审批的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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