拉力请求适合发布管道
我正在在Azure Devops中创建一个多阶段管道，以通过Terraform将基础结构部署为代码，并质疑在发布过程中应发生拉动请求...
我的管道有一个CI阶段，可以进行Terraform验证，有些测试等，然后单个阶段依次部署到每个环境。
当我创建PR时，触发管道运行CI和DEV部署阶段。在关闭PR并合并为MAIM之前，需要通过这些阶段的通过。
该策略听起来正确吗？我用来应用程序部署管道，其中PR的创建可能会触发部署到测试中以作为PR的条件运行自动测试。在IAC管道中，这似乎没有任何意义，因为通过部署进行测试并没有其他任何东西部署到DEV中，因为测试Env中没有任何其他测试。
有点困惑，想确保我的想法没有缺陷！在类似情况下其他人的经验将不胜感激。
I'm creating a multi-stage pipeline in Azure DevOps to deploy infrastructure as code via Terraform and have a question about when in the release process a pull request should occur...
My pipeline has a CI stage that does a terraform validate, some testing etc. and then individual stages to deploy to each environment in turn.
When I create a PR, the pipeline is triggered which runs the CI and dev deployment stages. Passing of these stages is required before closing the PR and merging into main.
Does that strategy sound correct? I'm used to application deployment pipelines where creation of a PR might trigger a deployment into test to run automated tests as a condition of the PR. In an IaC pipeline, this doesn't seem to make sense though because deploying through to test doesn't prove anything more than deploying into dev given that there aren't any additional tests run in the test env.
Bit confused and would like to make sure my thinking is not flawed! Experience of others in similar scenarios would be much appreciated.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
但是，该策略对我来说似乎还不错，但是，我建议您使用 terratest 作为的一部分您的CI流程可以定义特定的用例以验证部署的基础架构满足您的需求，这将使其类似于应用程序部署管道。
The strategy seems fine to me, however, I'd suggest you add a test stage using Terratest as part of your CI process so you can define specific use cases to verify that the infrastructure deployed meets your needs, this would make it similar to application deployment pipelines.