ci持续集成是干什么的_什么是持续集成（CI）？

ci持续集成是干什么的

Continuous integration is a process in which all the development activities (every day activities) are integrated at a given point of time by compiling and building the project and well tested. The basic idea behind the continuous integration is to ensure that there are no compilation issues at the end of the day by numerous check ins made by the developers in a team. Also, this would enable to identify any compilation issues at the early stages of the development process.

持续集成是一个过程，其中所有开发活动(日常活动)都通过编译和构建项目并在经过良好测试的情况下在给定的时间点进行集成。 持续集成背后的基本思想是，确保团队开发人员在无数次签入的情况下，最终不会出现编译问题。 而且，这将使您能够在开发过程的早期阶段确定任何编译问题。

In this process, all the developers activities are collaborated and merged at the central system (repository at which all the check ins are made). The main aim again here in this process is to eliminate the "integration problems". Each and every integration is automatically built, deployed and tested thoroughly.

在此过程中，所有开发人员活动都在中央系统(进行所有签入的存储库)处进行协作和合并。 在此过程中，这里的主要目标是消除“集成问题”。 每个集成都将自动进行自动构建，部署和全面测试。

关于CI的一些历史 (Some History about CI)

The phrase Continuous Integration was first coined by Grady Booch in 1994. He coined this phrase in object oriented analysis & design application in order to explain how the small internal releases plays a vital role while developing the micro processes. In 1997, an American software engineer named Kent Beck with another person named Ron Jeffries invented Extreme Programming with the continuous integration.

连续集成这个词最早是由Grady Booch于1994年提出的。他在面向对象的分析和设计应用程序中创造了这个词，目的是解释小的内部释放在开发微过程中如何发挥至关重要的作用。 1997年，一位名叫Kent Beck的美国软件工程师与另一个名叫Ron Jeffries的人发明了持续集成的极限编程 。

Continuous Integration (CI) was originally invented in order to be used with the combination of automated unit tests written in a test driven development environment. i.e to run all the unit tests in the local environment of the developer's machine and ensure that all the tests were passed successfully without any other issues before it is pushed into the main repository. This was an extra care taken in order to avoid any breakages on the working copies at the main streams especially when developers are working at the same module.

连续集成(CI)最初是为了与在测试驱动的开发环境中编写的自动化单元测试结合使用而开发的。 也就是说，要在开发人员机器的本地环境中运行所有单元测试，并确保所有测试均已成功通过且没有任何其他问题，然后再将其推送到主存储库中。 为了避免在主流上的工作副本出现任何损坏，这是特别需要注意的，特别是当开发人员在同一模块上工作时。

CI的最佳做法 (Best Practices of CI)

1. Maintain a proper code repository.

   维护适当的代码存储库。

2. Automate the build process.

   自动化构建过程。

3. Ensure every developer commits the files to the main stream every day.

   确保每个开发人员每天都将文件提交到主流。

4. Every commits made should be built.

   每个提交都应该构建。

5. Results of the build should be made transparent, so that all the developers will be aware of the quality of the build every day.

   构建的结果应透明化，以便所有开发人员每天都知道构建的质量。

6. Test the build in a production look-like environment.

   在生产环境中测试构建。

7. Broken builds should be fixed immediately.

   损坏的构件应立即修复。

8. Everyone should be able to get the latest build from the main stream.

   每个人都应该能够从主流获得最新版本。

9. Automate the deployment process.

   自动化部署过程。

CI的优势 (Advantages of CI)

1. Reduced level of risk.

   降低风险水平。

2. No longer integration process.

   不再集成过程。

3. Lot of bad code smells & bugs can be reduced at the early stages of the development process.

   在开发过程的早期阶段，可以减少许多不良的代码气味和错误。

4. Frequent deployment process is easier and faster.

   频繁的部署过程更加轻松快捷。

5. Easy to implement the process by using tools like Jenkins (earlier known as Hudson) and cruise control.

   使用Jenkins(以前称为Hudson)和巡航控制之类的工具可以轻松实现该过程。

翻译自: https://www.studytonight.com/jenkins/continuous-integration-overview

ci持续集成是干什么的