continuous integration and continuous deployment tools

Integration practicesThe typical tool for continuous integration is the open source system Jenkins. Through the research on the application of Jenkins Tools, a full-line software development diagram is drawn, as follows:650) this.width=650; "Src=" http://images2015.cnblogs.com/blog/111649/201512/111649-201512282021504

Currently, there are few teams and no Testers in the real sense. How can we ensure the code quality? I recently read the "continuous delivery-System Method for releasing reliable software", which was very inspired. I suddenly figured out the design concepts of many integrated development tools and made some practices, A special record is recorded and shared with everyone. How to Ensure code Quality I think

This article has been published in the "continuous integration" column on the infoq Chinese site. For more articles and video resources on "continuous integration" and "continuous delivery", visit "continuous delivery Chinese site

Build a continuous integration environment with MSBuild and Jenkins You or others have just finished writing a piece of code and submitted it to the project version repository. But what if the newly submitted code breaks down the build? What if a compilation error occurs, some tests fail, or the Code does not meet the requirements of quality standards? The most unreliable solution is to hope that everyone i

Automated deployment is one of the most important aspects of automated operations, and if a company often calls for automated operations, but does not have the concept of continuous integration, does not implement automated deployment, and requires programmers to manually package the

and KBM. There are integration tests, security scans, performance testing, and jar inspection, which are tools that other business teams do, and we integrate them into our release systems to enhance these capabilities. The road to Practice Fundamentals of Operations-standardization First of all, the basic software and configuration standardization, OS, JDK, Tomcat, Nginx and so on for operations to provide

Continuous Integration PairCodeThe database can be integrated at any time. The earlier the code set is, the earlier the defect is discovered. The lower the cost of fixing the defect, the lower the time and cost. Continuous integration preparation Version Control Include product code, test

The continuous integration environment requires an automated build tool, a code repository, and a CI server. To practice the code in this tutorial, you need to install the Java platform as well as Hudson 1.150, Ant 1.7, JUnit 3.8.1, and Subversion 1.4.x. For this tutorial, the recommended system configuration is as follows: A system that supports Sun JDK 1.5.0_09 (or later) or IBM Developer Kit for Java

key to continuous developer-centric integration is the rapid feedback of building software. In enterprise development, building management and controllable build processes are critical factors. A controlled build process regulates a series of steps to get source code, compile, package, and store.Most projects start with the development of the machine to build, and there is no standard process. This develop

Building continuous integration first of all to understand what is continuous integration, with a clear goal to build a continuous integration environment in order to let us go a lot less detours.

Connection and difference between daily build and continuous integration 1) continuous integration emphasizes a fast feedback.For example, when I check in the code, I immediately integrate it and give me a feedback. I want to know if my code has destroyed the build.Continuous integ