如何詹金斯有助于自动部署过程 [英] How is Jenkins helpful to automate deployment process
问题描述
谁能提供了使用詹金斯在可控和不可控enviroments自动化部署的见解。我们有不同的环境 - 开发/ QA / UAT /生产，目前我们正在使用调用的MSBuild /恶性脚本，Web和数据库服务器（Web场）部署批处理文件。开发者只能访问开发/ QA和生产支持将部署在UAT /刺。刺。支持将得到SVN标记文件夹中的源$ C $ c和运行批处理文件来部署应用程序。
Can anyone provide insights of using Jenkins for automating deployment under controlled and uncontrolled enviroments. We have different environments - dev/qa/uat/prod and currently we are using batch files that call msbuild/nant scripts to deploy on web and DB servers (web farm). Developers only have access to dev/qa and production support will deploy on uat/prod. Prod. support will get the source code from SVN tag folder and run the batch file to deploy the application.
通过使用詹金斯，是有可能消除督促的步骤。支持团队通过运行通过URL使用其凭据的作业正从SVN脚本。什么是使用源代码控制和部署应用程序CI工具的一般做法。
By using Jenkins, is it possible to eliminate the step of prod. support team getting the script from SVN by running the jobs using their credentials via url. And what is the general practice using source control and CI tool for deploying applications.
推荐答案
我的建议是保留詹金斯只是构建软件。这样，詹金斯的用户只能访问开发和QA或者系统。
My recommendation is to reserve Jenkins for just building the software. That way the user of Jenkins only have access to development and perhaps QA systems.
要从该部署我建议喜欢使用二进制仓库管理器软件的过程中解耦构建系统：
To decouple the build system from the process that deploys the software I recommend the use of a binary repository manager like:
- Nexus
- Artifactory
- Archiva
在这样的部署脚本可以检索previous构建的任何版本。使用一个仓库管理器将使您的QA团队用于验证发布之前它部署到生产。
In that way deployment scripts could retrieve any version of a previous build. The use of a repository manager would enable your QA team to certify a release prior to it's deployment onto production.
最后，考虑新兴部署自动化的工具之一。工具，如厨师，的木偶， Rundeck 可用于进一步的版本控制基础设施的配置。
Finally, consider one of the emerging deployment automation tools. Tools like Chef, Puppet, Rundeck can be used to further version control the configuration of your infrastructure.
这篇关于如何詹金斯有助于自动部署过程的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
