continuous integration and continuous delivery tools

= "Run tools in parallel" >description= "Prepare for Build" >description= "Find coding standard violations using Php_codesniffer creating a log file for the continuous integration serv ER ">============end===============Configuration of the PHPUnit============phpunit.xml=========================end=================Enter Jenkins's task directory, typically in:/var

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 focu

affect the development efficiency, and local hardware conditions may not start 3, if the local do not build submissions, because of the large number of developers, the build will be very unstable, will often be in a failed state. A build failure can cause subsequent commit blocking. 4, as a 100-person development team, code submission will cause frequent server building, the server can not afford. At the same time as customers, they have the idea that agile development is good, but not suita

In implementing continuous delivery, we can easily focus on automation and tools, because they are usually the easiest to do as a starting point. However, the successful implementation of continuous delivery also relies on the optimization of the organizational structure bas

"alt=" Wkiom1lp3swrgc_aaacqu12l-qm061.png "/>650) this.width=650; "src=" Https://s2.51cto.com/wyfs02/M00/99/FD/wKiom1lP3tjxpMifAAAPmu6l7x0172.png "title=" W] 1gi4vtc}qaetk2wfe4ojn.png "alt=" Wkiom1lp3tjxpmifaaapmu6l7x0172.png "/>Select Install plugin, left for all plugins, right to customize installation650) this.width=650; "src=" Https://s4.51cto.com/wyfs02/M01/99/FD/wKioL1lP3yXQlC_8AADxPLi5y1o647.png "title=" NVA8 " ZU4VIPNH7CU%[C) ynt.png "alt=" Wkiol1lp3yxqlc_8aadxpli5y1o647.png "/>When the

. Although the integrated code succeeds in working together, it is not ready for the production environment because it has not been tested and validated in a simulated production environment. You can read more about what happens after continuous integration in the Continuous delivery section below. Figure 1 To maintai

Vagrant or Docker from the configuration, we use Docker technology internally to isolate the various build environments.Pipeline3.2.2 Deployment PipelineAs the name implies, this step is to deploy packaged software to a different operating environment, and to automatically handle the configuration of each environment (such as domain name, database information, login information, etc.), this step relies heavily on the implementation of the previous steps, warehouse planning, branch planning,