gpt4 book ai didi

Bamboo 构建计划与自定义环境配置的部署计划

转载 作者:行者123 更新时间:2023-12-04 11:39:12 24 4
gpt4 key购买 nike

我正在评估 Bamboo 以取代我们的 Jenkins 设置,并有几个问题。我有一个 .NET 解决方案,它生成两个工件:一个打包的网站和一个 MSI。我部署了三个环境:测试、阶段、生产。我们的 Jenkins 服务器依次具有三个作业——每个环境一个。每个作业构建解决方案,将其部署到的环境的配置文件中复制,然后部署工件。阅读文档和其他内容( https://answers.atlassian.com/questions/19562/plans-stages-jobs-best-practices ),我收到了关于部署应该如何与 Bamboo 一起工作的混合信号。在我看来,部署计划希望工件存在,然后部署它们。但是,构建计划也包括部署步骤。所有这些应该如何相互作用?

我感到困惑的原因是因为我有在构建过程中打包的特定于环境的配置文件。关于这应该如何工作的任何方向?

最佳答案

我也将问题发布到了 Atlassian 板并得到了 an answer我认为我最喜欢:

Jason Monsorno · 762 karma · Aug 30 '13 at 04:38 PM

Deployment projects in Bamboo seem to be dependant on the existance of an artifact, the catch is you don't necessary need to use that artifact so you could use an empty artifact and do completely independent steps. Deployment projects are still fairly new to Bamboo and your structure may favor the "normal" workflow so each environment would be a separate manual stage.

The Deployment project do have a separate workflow and versioning. To use Deployment projects in your scenario, I'd suggest making the artifact the entire checkout then each Deployment environment can build a copy of the artifact. The space-saving/less-time-efficient option would be to just save the current revision in a file as the artifact and use that to check it out and build in each Deployment environment.

关于Bamboo 构建计划与自定义环境配置的部署计划,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/18540675/

24 4 0
Copyright 2021 - 2024 cfsdn All Rights Reserved 蜀ICP备2022000587号
广告合作:1813099741@qq.com 6ren.com