Continuous integration tools and environment setup

Continuous integration tools

Automation is an effective way to efficiently carry out continuous integration activities, which everyone knows. So how can we achieve automation? Are there any ready-made tools that can be used 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. You can safely use these open-source free software because many excellent open-source software are developed in the continuous integration environment built by these tools and software. Below I will give a brief introduction to several important open-source tools.

• Eclipse: eclipse is an open-source ide tailored to programmers. Its biggest feature is that it draws on the idea of the Smalltalk development environment to present its internal working principles to users in some way, users can follow some principles to change the development environment as needed. In eclipse, this mechanism operates in Plug-In mode. In this way, you can easily integrate common tools in the development process and present them in your own way. For example, tools such as refactoring, JUnit, and cvs can be easily integrated into the eclipse unified development platform to provide a good operating platform for continuous integration.
• CVS: CVS is an open-source version control tool software. Compared with some expensive commercial software of the same type, it provides few functions, however, these features are sufficient for most software development teams. CVS provides the development team with a time machine within the project scope. The team can easily and accurately obtain the project status at a specified time. In addition, CVS also provides tag and Branch functions, which provide the foundation for the team to perform multi-branch parallel development without worrying about the loss of work results.
• Cruisecontrol: cruisecontrol is a continuous building process framework that provides external scaling mechanisms. Using the Plugins mechanism of cruisecontrol, you can easily integrate various source code control tools and build tools, in addition, you can provide external interfaces such as email notification and Web display for the current and historical build statuses. It is through this tool that continuous integration can be customized and automated.

Well, the introduction of the tool is here. below is our journey to build a continuous integration environment. This article does not introduce too much knowledge about refactoring technology, Eclipse, JUnit, and CVS. It focuses on how to integrate these tools to build a continuous integration environment, readers can refer to related books on their own.

Back to Top

Tutorial on building a continuous integration environment

The following describes how to use the three open-source tools to build a continuous integration environment.

1. Download tool software

You can download the tool software required to build a continuous integration environment on the website. These software are open source and can be downloaded and used for free.

• Download eclipse from http://www.eclipse.org.
• Download CVS from http://www.cvsnt.com
• Download cruisecontrol from http://cruisecontrol.sourceforge.net

2. install and configure CVS

CVS is developed based on SCCs and RCS in UNIX systems and is used for source code version management. It is a Client/Server structure product and can be used on multiple platforms (Linux and Windows ), at present, it has become one of the mainstream products for software developers to manage versions in the development process (especially the development of open source software ). The main function of CVS is to record the history of source files in the software development process on the CVS server. When developers in the same group develop the same project, CVs will differentiate them, so that each developer can perform independent development work on their own clients, after a developer submits a new file to the CVS server, the CVS Resource Library collects statistics to detect conflicts and merge them.

You can download the latest version of cvsnt from the http://www.cvsnt.com, the author from the website down version is 2.0.58d. Double-click the execution file to install it. The environment variable is automatically added during installation to indicate the installation path of CVS.

Select Start-Program-cvsnt-service control panel. You can see that the CVS server and the CVS lock server are started by default.

On the "repositories" page, click "add" and select the address for adding the CVS resource library to create a CVS resource library. In this example, the address is selected by the author based on the situation on his own machine, the reader can set according to his own environment.

Select the "advanced" page to confirm the "tempory" directory and the default user that runs. If the port does not conflict, the listening ports of the CVS server and the CVS lock Server do not need to be changed. Select "OK ". After the advanced options are changed, switch to the "service status" Page, stop the two services, and restart them.

At this point, our CVS server has been configured successfully and a resource library has been created.