That's not enough though; I suggest exercise your deployment scripts as part of a Continuous Integration build.
那还是不够的；我还建议把部署脚本看成持续集成构建的一部分去执行。
Continuous integration builds on this concept, but this also implies the ability to build outside the context of an ide.
持续集成(continuous integration)就是建立在这个概念的基础之上，但它也应用了在ide上下文之外的地方进行构建的能力。
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，持续集成服务器就可以在每当发生更改时签出项目，运行构建，并执行测试。
You can also use continuous integration tools for traditional development — to implement an automated nightly build process, for example.
你也可以将持续集成工具用于传统开发——例如，实施一个自动化的每夜构建过程。
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.
如果有适合的集成点，将构建和发布系统连接起来实行持续部署以达到真正的端到端自动化也是有可能的。
These are key aspect of the vision for "developer self-service" and "continuous integration" that automated build management brings into reality.
这些是对于自动构建管理带到现实中的“开发人员自服务”和“连续集成”的构想的重要方面。
A Continuous Integration environment requires an automated build tool, a code repository, and a CI server.
持续集成环境需要一个自动构建工具、一个代码存储库和一个CI服务器。
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.
这第一台构建服务器将会是你的持续集成服务器，它要保证每次签入动作都能成功构建。
As such, the build utility is a perfect tool to help automate the applications builds, when working in a continuous integration environment.
所以，构建工具是一种完美的工具，在持续性集成的环境下可以帮助您自动化程序的构建。
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 article covers only the build applications process using a continuous integration server.
本文只涉及到了使用一个持续性的集成服务器的构建程序过程。
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.
持续集成是每天运行多次的完全自动化和可再现的构建(包括测试)，是用于传统应用程序并得到广泛认可的开发实践。
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 is required so that the continuous integration server can build and test the SCA module.
只有这样，持续集成服务器才能构建和测试sca模块。
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服务器所做的已经远远不仅仅是将完整的构建流程自动化。
By using Eclipse plugins, however, you can uncover some of these violations before you build or integrate via Continuous Integration.
如果使用Eclipse插件，就可以在通过Continuous Integration构建或集成前发现一些这样的冲突。
I provide an overview of the different types of developer tests along with examples that you can add to your build process and run continually using a Continuous Integration system.
我提供一个关于不同类型开发人员测试的概览，和一些可以添加到构建过程并使用Continuous Integration系统持续运行的例子。
If you're running a Continuous Integration tool such as CruiseControl, you're probably familiar with the E-mail messages sent to the team when a build fails.
如果您在使用CruiseControl之类的持续集成工具，那么很可能熟悉当构建失败时发送给团队的电子邮件消息。
CruiseControl is a build process framework that supports several modes of integrating your project, including continuous integration, that have become quite popular.
CruiseControl是一种构建过程框架，它支持多种集成项目模式，包括已被广泛采用的持续集成。
We've then installed and set up the Hudson continuous integration server, and we've created a Hudson job that USES the build utility to finally produce the EAR file.
然后我们将会安装并创建Hudson持续性集成服务器，并创建一个Hudson任务，该任务会使用构建工具来最终生成EAR文件。
A build consisting of minimal automated processes, which results in builds that never fail, leading to Continuous Ignorance and delaying integration problems.
构建中只包含很少的自动过程，结果导致构建总是成功，造成持续忽视(Continuous Ignorance)和集成延迟问题。
For example, consider using Jazz source control and the Jazz build engine to power your continuous integration efforts.
例如，考虑使用源控制，以及Jazz构建引擎，来提高您的持续开发效率。
A third option is to create a new build option for your continuous integration server that includes a push to production step.
第三种选择是为持续集成服务器创建新的构建选项，其中包括推送到生产环境这一步。
In a continuous integration environment, programmers are writing code, running the build and tests on their own workstations, and checking in multiple times a day.
在持续集成的环境中，程序员需要编写代码，在工作站上运行构建和测试，一天内多次进行检入。
Obviously, a user can enter the command, but because it's so terse, it can be easily run by a headless process, such as a Continuous Integration or build-management 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.
把“持续改进和持续集成”加入到你的工具和流程中去，这也是运维人员向(优秀的)开发人员学习的好途径，可以学到诸如测试驱动开发等最佳实践。
Once you have the build servers and script necessary for continuous integration, the next question is always, “So what do we do with the builds?”
当你有了持续集成需要的构建服务器和脚本之后，下一个问题肯定是：“我们该拿这些构建版本怎么办？”
应用推荐