持续集成工具最近几年流行起来了。
Continuous integration tools have become popular in the last few years.
持续集成工具。
在将测试集成到开发环境方面它做得更好，它还有更好的持续集成工具。
It integrates testing into development environments better, and it has better continuous-integration tools.
你也可以将持续集成工具用于传统开发——例如，实施一个自动化的每夜构建过程。
You can also use continuous integration tools for traditional development — to implement an automated nightly build process, for example.
我使用了一个自举模式显示了持续集成工具的日志风格，他们往往是相当长的。
I'm using a bootstrap modal to display builds logs for a continuous integration-style tool, and they are often quite long.
如果您在使用CruiseControl之类的持续集成工具，那么很可能熟悉当构建失败时发送给团队的电子邮件消息。
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.
使用这样一个ant脚本，可以以一种自动化方式运行一些Selenium测试，方法是计划这些测试，或者在一个持续集成工具中使用这个ant脚本。
Using an Ant script like this one, you can run the Selenium tests in an automated fashion by scheduling them or using the Ant script in a continuous integration tool.
Twist也可以在任何持续集成环境中运行(随同t wist我们一起发布了一个自定义的Ant任务)，它的报表与JUnit兼容，所以你们的标准构建工具以及持续集成工具可以解析它们。
Twist also will run in any CI environment (and we ship with a custom ant task), and its reports are JUnit compliant, so your standard build and CI tools can parse them.
这个变更管理工具可以用来驱动一个完全自动化的持续集成和合并过程。
The change management tool can be used to drive a fully automated continuous integration and merge process.
例如，配置管理工具可以支持每日部署、增量式设计和持续集成。
For example, configuration management tool supports daily deployment, incremental design and continuous integration.
持续集成环境需要一个自动构建工具、一个代码存储库和一个CI服务器。
A Continuous Integration environment requires an automated build tool, a code repository, and a CI server.
使用工具(静态分析，单元测试，持续集成，自动化可接受性测试)来帮助团队发现、减少和衡量他们的技术债务量。
Use Tools (Static Analysis, Unit Test, Continuous Integration, Automated Acceptance Tests) to help the teams find, reduce and measure their debt load.
在这篇文章里，我将会讨论什么是持续集成，它适用于软件开发生命周期的哪些地方，以及如何用一个支持工具集来实现它。
In this article, I will discuss what continuous integration is, where it fits into the software development lifecycle, and how it can be realized with a supporting toolset.
把“持续改进和持续集成”加入到你的工具和流程中去，这也是运维人员向(优秀的)开发人员学习的好途径，可以学到诸如测试驱动开发等最佳实践。
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.
持续集成最初是由一组工具支持的一个过程。
Continuous integration is, first and foremost, a process backed by a set of tools. Martin Fowler and Matthew Foemmel define it as 1.
所有这些可能会把持续集成理论和工具的焦点从构建转移到测试上来。于是，一个修改过的(持续集成)的定义为。
All of this though, is only possible by shifting the focus of CI theory and tooling from build to test. As such, a revised definition would be.
并且这种局面现在就在发生，我的老板，Urbancode，已经在CI服务器上利用了测试的方法到持续集成中，其它的一些工具最近也会开始符合这一策略。
And this is happening right now. My employer, Urbancode, has used the test approach to CI in its CI Server for some time now, and other tools have recently started to adopt this strategy as well.
并且这种局面现在就在发生，我的老板，Urbancode，已经在CI服务器上利用了测试的方法到持续集成中，其它的一些工具最近也会开始符合这一策略。
And this is happening right now. My employer, Urbancode, has used the test approach to CI in its CI Server for some time now, and other tools have recently started to adopt this strategy as well.
应用推荐