CruiseControl: Framework for a continuous build process.
CruiseControl：用于持续构建过程的框架。
It is a framework for a continuous build process. Using CruiseControl you could.
这是一个用于持续构建流程的框架。
Tests should be automated as much as possible and run as part of the daily or continuous build.
测试应尽可能自动完成，并作为每日构建和持续构建的一部分运行。
For example, daily deployment practice requires unit testing, configuration management and continuous build.
比如，每日部署实践需要单元测试、配置管理和持续构建的支持。
What's needed is something highly visible, like a canary, that I can quickly glance at to see the state of my continuous build process.
这时需要某种高度可视的东西，就像金丝雀一样，快速一瞥后就能发现持续构建过程的状态。
In this article, we propose an architecture using Rule Team Server and DVS to implement a continuous build system for WebSphere ILOG Rules.
在本文中，我们建议使用一个架构，用RuleTeamServer和DVS实现WebSphereILOGRules持续构建系统。
What's needed is something highly visible, like a canary , that I can quickly glance at to see the state of my continuous build process.
这时需要某种高度可视的东西，就像金丝雀一样，快速一瞥后就能发现持续构建过程的状态。
Measurements from a continuous build and automated testing process will give you valuable insight into overall project progress and health.
来自连续的构建和自动化测试过程的度量将会让您对整个项目的过程和全面状况有一个非常好的了解。
You can also use the Builds check-in policy as a tool to limit additional changes to your code base until a continuous build break is fixed.
您也可以使用作为工具的组建签入原则，来限制到您的程序码基底的额外的变更，直到连续建置中断固定。
If you have a continuous build process, allowing you to build anytime there are significant changes that could be tested, you will have lots of data to assess progress.
如果您有个连续的构建过程，您就可以在可被测试到的重大变化发生的任何时候进行构建，您将会有很多数据来评估过程。
In the Downloads section, you will find a sample implementation of a continuous build system for Rule Team Server and DVS, using the principles and pieces of code described in this article.
在下载部分，您将找到一个适用于RuleTeamServer和DVS的持续构建系统的样例实现，并且可以使用本文介绍的准则和代码片段。
That's not enough though; I suggest exercise your deployment scripts as part of a Continuous Integration build.
那还是不够的；我还建议把部署脚本看成持续集成构建的一部分去执行。
If a build running on your Continuous Integration system fails, you can be fairly certain the cause lies in the most recent change.
如果在持续集成系统上运行的构建失败，那么可以肯定失败的原因出在最近的更改中。
A Continuous Integration server constantly checks the code out of source control, builds it, runs the unit tests against it, and reports any build failures to the developers, usually via E-mail.
持续集成服务器不断检查不受源控制的代码，执行构建，对它运行单元测试，并通常通过电子邮件向开发人员报告所有构建故障。
Once in CVS then the continuous integration server can check the projects out whenever there is a change, run the build, and execute the tests.
一旦将项目签入了CVS，持续集成服务器就可以在每当发生更改时签出项目，运行构建，并执行测试。
With suitable integration points, it is even possible to connect to build and release systems and realize continuous deployment for true end-to-end automation.
如果有适合的集成点，将构建和发布系统连接起来实行持续部署以达到真正的端到端自动化也是有可能的。
A Continuous Integration environment requires an automated build tool, a code repository, and a CI server.
持续集成环境需要一个自动构建工具、一个代码存储库和一个CI服务器。
These are key aspect of the vision for "developer self-service" and "continuous integration" that automated build management brings into reality.
这些是对于自动构建管理带到现实中的“开发人员自服务”和“连续集成”的构想的重要方面。
You can also use continuous integration tools for traditional development — to implement an automated nightly build process, for example.
你也可以将持续集成工具用于传统开发——例如，实施一个自动化的每夜构建过程。
Continuous integration can mean building many times a day, every twenty minutes, every hour, or even just once a day (as part of a nightly build).
持续集成可以预定一天构建多次，每二十分钟，每个小时，或者每天只进行一次(作为每夜构建的一部分)。
This first build server will also be your continuous integration server. It is the one that ensures that every single check-in can be built.
这第一台构建服务器将会是你的持续集成服务器，它要保证每次签入动作都能成功构建。
Continuous integration, a fully automated and reproducible build (including testing) that runs many times a day, is a well accepted development practice for traditional applications.
持续集成是每天运行多次的完全自动化和可再现的构建(包括测试)，是用于传统应用程序并得到广泛认可的开发实践。
As such, the build utility is a perfect tool to help automate the applications builds, when working in a continuous integration environment.
所以，构建工具是一种完美的工具，在持续性集成的环境下可以帮助您自动化程序的构建。
Under the continuous delivery philosophy QA has only two options for handling a given build that it receives. The build can either be failed or be promoted to staging.
在持续交付思想指导下，QA对于接收到的给定构建版本，只有两个选项：构建要么失败，要么提送到交付准备服务器。
Tests can also be added to a continuous integration environment and asserted against service functionality with each build.
也可以把测试添加到一个持续集成环境中，然后拿每个版本对照服务功能进行断言。
When done properly, continuous integration can significantly increase developer productivity, in part by providing team members with immediate feedback via email if the build breaks.
当正确地完成后，持续集成可以显著地增加开发人员的工作效率，部分是通过在构建中断时立即用邮件将反馈提供给团队成员。
This is required so that the continuous integration server can build and test the SCA module.
只有这样，持续集成服务器才能构建和测试sca模块。
This article covers only the build applications process using a continuous integration server.
本文只涉及到了使用一个持续性的集成服务器的构建程序过程。
Build continuous improvement and integration into your tools and processes. Here is a good place operations people can learn from (good) developers about practises like test-driven development.
把“持续改进和持续集成”加入到你的工具和流程中去，这也是运维人员向(优秀的)开发人员学习的好途径，可以学到诸如测试驱动开发等最佳实践。
As the discussion in Agile development moves from continuous integration (CI) to continuous deployment, CI servers are doing more to automate the overall build process.
正如关于敏捷开发的讨论由持续集成转向到敏捷部署，CI服务器所做的已经远远不仅仅是将完整的构建流程自动化。
应用推荐