持续交付和拉取请求会触发新版本 [英] Continuous Delivery and Pull Requests triggers a new release

查看:70
本文介绍了持续交付和拉取请求会触发新版本的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

在VSTS中,我们配置了构建,因此最终结果将是单个工件。


我们还配置了相关版本,以便在新工件发布后创建新版本创建。


我们还配置了版本,以便在发布新版本时将应用程序连续部署到环境(分段,生产等)。


这意味着当构建成功时,新版本将自动部署到生产环境。 



我们在主分支上启用Pull请求并配置到达pull请求应该导致构建。使用"合并"触发构建。标签。 


一切正常,但使用我们的构建版本配置,每个拉取请求也会自动部署到所有环境。由于在"合并"时也创建了新的工件。构建。


虽然构建成功,但我们只想在拉请求再次与master合并之后部署应用程序。


简而言之:是否有可能"合并"。由Pull Request触发的Build不会产生新版本吗?

解决方案


感谢您在此发布。


我们已经与技术团队检查了您的查询,因为相同的构建定义与PR相关联,并且使用该定义的正常构建在发布中。在这种情况下,在分支过滤器中指定master将仅使用已合并
的构建,并且此功能应尽快部署。


告诉我们反馈,以便我们可以为您提供更多查询帮助。


希望这会有所帮助!


问候,


_______________________________________________________________________________________________________


如果帖子回答了您的问题,请点击该帖子上的标记为答案  投票为有用


In VSTS we configured the builds so the final result will be a single artifact.

We also configured the correlating releases to create a new release after a new artifact has been created.

We also configured the releases to continuously deploy the application to the environments (Staging, Production, etc) when a new has been released.

This means that when a build is successfull, in the end the new version will be automatically deployed to the production environment. 

We enabled Pull Requests on the master branch and configured that reach pull request should result in a build. The build is triggered with a "merge" label. 

All works fine, but using our build-release configuration, each pull request also automatically gets deployed to all environments. Since a new artifact is also created when on the "merge" build.

Although the build is successfull, we would like to only deploy the the application after the pull request has been merged with master again.

In short: is it possible that a "merge" Build, which is triggered by a Pull Request, doesn't result in a new Release?

解决方案

Hi,

Thanks for posting here.

We have checked your query with the Technical team, as per them same build definition is linked to PRs and normal builds from that definition are consumed in releases. In this case, specifying master in the branch filter will only consume the builds that have been merged and this feature is expected to deploy as soon as possible.

Let us know the feedback so that we can assist you more on your query.

Hope this helps!

Regards,

_______________________________________________________________________________________________________

If a post answers your question, please click Mark as Answer on that post and Vote as Helpful.


这篇关于持续交付和拉取请求会触发新版本的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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