Jez masterpiece continuous delivery (translated in Chinese)

Jez (thoughtworker) masterpiece "continuous delivery" was published. Martin Fowler (another thoughtworker) in order and included in the Martin Signature Series. The Chinese version of this book is being translated by Qiao Liang and others (including me). The Chinese version is estimated to be coming next year.

However, I will give a speech on this topic at the agile China conference in March. I am talking about the path to continuous delivery of agile organizations. I have seen a lot of companies unable to achieve continuous integration. I can't say that he didn't make up his mind. The server was shelved, the CC was installed, and it went on for a week. In the future, they will be put there for special visits and use by leaders. Why? Continuous integration fails, but it is difficult to locate the problem. As a matter of fact, lauma has long discussed this issue, and no one will check it there. Everyone is working on continuous integration. In the field of continuous integration, we often use the term "build )". Many people think that "build = compilation + Link (build = compile + link)", Martin pointed out in the first version that a successful build includes:

• all the latest Code is retrieved from the configuration management tool (check out or update ).
• all code is compiled from a clean state.
• link and deploy the compilation result for execution.
• run the deployed application and test set.
• if all the preceding operations have no errors, no manual intervention, and all tests have passed, we think this is a successful build.

In fact, at present, many teams have defined the successful continuous integration build basically in line with the above definition. This definition is characteristic of its relative independence, it is a process in which the Source Code of the clean state is used to finally obtain the software that can run the verification.
In the second version, Martin defines successful integration based on successful build. Successful integration focuses not on the "Compilation + link + deployment + Verification" process, but on a complete code submission process under the constraints of continuous integration from the perspective of the development process. I will slightly process the format, which is slightly different from the original one. :

• Copy the integrated source code to the local computer.
• Modify product code and add and modify automated testing.
• Start an automated build on your computer.
• After the build is successful, update others' modifications to my work copy.
• Then re-build.
• Submit the changes to the source code repository.
• Build again on the integrated computer and based on the main line code.
• Only when this build is successful can the changes be successfully integrated.

Demonstrate Martin's definition of successful integration:

Of course, in the "Code commit" section of the first version, Martin also mentioned the concept of local build, but it is not as clear as the second version.

I will introduce a case in more detail at the conference. In addition to the process described above, it also includes configuration management, environment management, test reorganization, and organizational structure adjustment. After the handouts are opened, they will be posted to the blog.

Welcome to the agile China conference.