Continuous integration Case Analysis Series (1)-continuous integration of small-scale product teams

A year ago, Li Jian (Editor of the agile community on infoq Chinese site) proposed to write some practices and examples used in practical agile software development projects, so I decided to summarize my actual project and consulting experience. Since we have been working in the field of "continuous integration and release management", we will not spend any time thinking about the subject. We will only focus on continuous integration, summarize the projects and situations encountered during the consulting process.

 

Naturally, it is the "Cruise" of your project. Therefore, "continuous integration" also needs reconstruction-evolution of continuous integration practices in the development of Cruise "was written at the end of February, with the help of Derek, Li, and Li Jian, a colleague, finalized at the end of March and released on the infoq Chinese site.

 

This article describes the continuous integration process and environment of the cruise product team, discusses the original motivation of continuous integration, and several continuous integration modes generated over time, as well as their respective advantages and disadvantages. These modes include: (1) simple type; (2) Step type; (3) process type; (4) pipeline type.

 

Pipeline continuous integration is similar to procedural continuous integration, but its concept is significantly different. In pipeline continuous integration, all process units run in the context of the same pipeline, that is, the raw materials used by each unit are the same, that is, the Code baseline is the same. When a new code is found on the continuous integration server, a new pipeline is created and all process units are running in the pipeline. The product generated by each unit is also valid in this pipeline..

 

Because cruise is currently only an independent product with not too many code and no dependency, and the team size is not large, its continuous integration environment is not complex. It can be regarded as a continuous integration solution for small-scale product teams. This is the case, but I believe most teams in China may still fail to reach this point. However, without starting from the first step of the Great Wall, you may never be able to imagine the fruits and charm of continuous integration.