詹金斯 - 促进构建不同的环境 [英] Jenkins - Promoting a build to different environments

问题描述

我希望的的最佳方式一些指导通过其环境，促进构建。

I was hoping for some guidance on the best way to promote a build through its environments.

我们有3个环境，DEV，分期，PROD。

We have 3 environments, DEV, STAGING, PROD.

该DEV詹金斯建立在持续集成建立运行，为code为检查颠覆，詹金斯将运行新的版本（清洁，编译，测试，部署）。

The DEV Jenkins build is running in a continuous integration set-up, as code is checked in to subversion, Jenkins will run a new build (clean, compile, test, deploy).

棘手位是当它涉及到分期和PROD。

The tricky bit is when it comes to STAGING and PROD.

当时的想法是能够手动推广成功的DEV建立以分期。
分期建设将检查出的DEV的SVN版本号，构建，测试，部署到分期终于在SVN创建一个分支。

The idea was to be able to manually promote a successful DEV build to STAGING. STAGING build would check out the DEV's SVN Revision number, build, test, deploy to staging and finally create a branch in SVN.

最后发布管理员可以手动促进分期建设督促。
PROD构建想看看从previous分期建设分公司，部署到PROD和触杀分支作为释放。

Lastly the release manager could manually promote the STAGING build to PROD. PROD build would check out the branch from the previous STAGING build, deploy to PROD and tag the branch as a release.

我曾尝试使用促进组合构建插件和Paramterized触发插件，但没有运气。 Subversion修订数字似乎并没有获得通过DEV之间建立以分期建设。

I have tried to use a combination of the Promotion Builds Plugin and the Paramterized Trigger Plugin but with no luck. The Subversion Revision number doesn't seem to get passed between DEV build to STAGING build.

有没有人对他们的过程的任何指导，通过多种环境，促进构建？

Does anyone have any guidance on their process to promote a build through multiple environments?

推荐答案

在这种情况下，为什么你需要回去和SVN标签的分支？我们不使用SVN，但瓦特/ TFS，当哈德森/詹金斯得到code，它已检索到的变更号码在构建日志。因此，我们知道什么code编译来自，并且可以随时取回它。

In this scenario, why do you need to go back and label the branch in svn? We don't use svn, but w/ TFS, when Hudson/Jenkins gets the code, the changeset number it has retrieved is in the build log. So we know what code the build came from, and could get back to it at any time.

然后我们使用哈德森促进从环境构建环境，源代码控制系统并不需要知道在哪里code部署。

Then we promote the build from environment to environment using Hudson, the source control system doesn't need to know where the code is deployed.

这篇关于詹金斯 - 促进构建不同的环境的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！