Continuous integration tools and environments

Introduction to Continuous integration tools

An effective way to efficiently carry out continuous integration activities is to automate, which is not to mention everyone knows. So how can automation be achieved. Are there any ready-made tools that you can use directly? The answer is yes. In addition to the expensive commercial tool software, there are many easy-to-use and very effective open source free software available. For these open-source freeware, you can rest assured that many of the very best Open-source software is developed in the continuous integration environment built by these tools. Here's a brief introduction to some of the more important open source tools. Eclipse:eclipse is an Open-source IDE that is tailored for programmers. Its biggest characteristic is that it borrows from the thought of the Smalltalk development environment, can put its internal working principle in some way to display in front of the user, the user can follow some principle to change this development environment according to own need. In eclipse, this mechanism operates through a plug-in approach. In this way, users can easily integrate the tools commonly used in the development process and present them in a way that is easy for them to use. For example, you can easily integrate tools such as refactoring, JUnit, and CVS into the unified development platform of Eclipse, providing a good platform for continuous integration. Cvs:cvs is an open source version control tool software that offers few features compared to expensive, similar commercial software, but these features are sufficient for most software development teams. CVS provides a project-wide time machine for the development team. Through it, the team can easily and accurately obtain the project at a specified time of the situation. In addition to this, CVS provides the tag and branch features that provide the basis for a team's multiple-branched parallel development and do not worry about the loss of work results. Cruisecontrol:cruisecontrol is a continuous build process framework, and it provides a mechanism for scaling. Using the CruiseControl plugins mechanism, users can easily integrate the various required source control tools and build tools, and provide external interfaces such as email notifications and web displays for current and historical build states. It is through this tool that the continuous integration can be customized and automated.

Well, here's the tool introduction, and here's our continuous integration environment. This article does not do much about the knowledge of refactoring technology, Eclipse, JUnit, and CVS itself, focusing on how these tools can be integrated to build a continuous integration environment, with the basic knowledge that readers may refer to relevant books themselves.

Back to the top of the page

A tutorial on continuous integrated environment

Here's how I use the three open source tools above to build a continuous integration environment and summarize it to chiselled readers.

1 Download of tool software

Readers can go to the Web site to download the tool software needed to build a continuous integration environment, which is open source, and can be downloaded and used for free. Download Eclipse to http://www.eclipse.org. To http://www.cvsnt.com download cvs to http://cruisecontrol.sourceforge.net download CruiseControl

2 Installing, configuring CVS

CVS is a product developed on the basis of SCCS and RCS in UNIX systems for source version management. It is a client/server architecture product that can be used on a variety of platforms (linux,windows) and is now developed as one of the mainstream products of software developers for versioning during development (especially open source software development). The primary function of CVS is to record the history of the source files in the software development process in the CVS server. When developers of the same group develop the same project, CVS differentiates them so that each developer can work independently on their own clients, and after the developer submits a new file to the CVS server, the CVS resource pool counts for conflict detection and consolidation.

Can download the latest version from the Http://www.cvsnt.com cvsnt, the author from the site down the version is 2.0.58d. Double-click the Execute file, install, and automatically add environment variables during installation to represent the CVS installation path.

Select Start-Program-cvsnt-service Control Panel, as shown in the figure, and the CVS server and the CVS lock server are already activated by default.

Select the "Repositories" page, click the "Add" button, and select the address of the CVS repository to create a CVS repository. In this case the choice of address is based on the author's own machine situation, the reader can be set according to their own environment.

Select the "Advanced" page to confirm the "tempory" directory and the default user running. As long as there is no conflict between the ports, the CVS server and the CVS lock server's listening port need not be changed, choose OK. After you change the advanced options, switch to the service Status page, stop the two services, and then restart.

By this, our CVS server has been configured successfully and a resource pool has been created.