Use SVN + cruisecontrol + ant for continuous integration 3-build operations and monitoring

Use cruisecontrol + SVN + ant for continuous integration 3
-- Build operations and monitoring

In the previous section, we introduced environment setup and configuration, and started CC quickly to view the integration results. In this section, we will introduce CC build operations and monitoring in detail.
1. Start the CC Server
Run the cruisecontrol. BAT file in the root directory to start CC. If "buildqueue-buildqueue started" is displayed on the console, the CC server is successfully started.

Before starting the server, we can open the cruisecontrol. BAT file and modify the port value of the corresponding function in the last row to specify the system Port occupied by the server. In this example, we will set the default port 8080.

 

2. Report Management
In the previous section, we introduced that CC has two portals for managing integration projects. CC provided the report method to control the main interface earlier, and accessed through http: // localhost: 8080/cruisecontrol, the interface is as follows:

The information about each project is displayed in the list, including the current status, last failed time, last successful time, and number of builds. At the same time, the build button allows CC to check the project status immediately. Click the name of the project to go to the home page of the project details page. The home page is clear and clear, including the construction history, recent build results, and recent build version information, this page allows us to view the integration information of the current project at a glance, so that we can process different integration results accordingly. The navigation buttons on the top of the page allow us to go to the View Interface for different information, including the building result, test result, XML detailed log file, status statistics, application configuration, console configuration, and other information. These navigation buttons vary depending on the extended tasks set by the project.

2.1. Build results
The top of the first tag page displays the basic information about the latest build of the project (including the build date, time, and latest modification time of the project file), warnings and errors during compilation, automated test results, and detailed details of the project changes.

2.2. Test Results
The tag page shows the automated test results. The results are classified by test class, and the test results and time of each method are displayed under each test class. Logs are output from the console in each test class. Click "system. Out" to view the specific log information.

2.3. xml detailed log file
Record all construction information of the project, as shown in.
This file records the basic information of the project, the last build time, the last successful build time, and the build time. It also includes the project configuration information, such as JDK version and operating system construction.

2.4. Status statistics
The tag page displays the Project Build status information through different types of graphs. The total build count, successful count, and failure count of the page are displayed at the top of the tag page, next, we will use a pie chart to show statistics such as the number of successes and failures.

 

2.5. Application configuration
CC supports configuring config on the page. XML file, you can first load the configuration information of the application through "reload from server". The configuration content includes listeners, bootstrappers, source controls, schedule, log, publishers, and other nodes, after modification, click "OK" to save the configuration information.

2.6. Console Configuration
On the tag page, you can configure the project control, including the building polling time, version tag number, and release package naming format.

 

3. Dashboard Management
Currently, we usually use the dashboard interface (also recommended for CC) to manage project integration. Its address is http: // localhost: 8080/dashboard. This method uses color blocks of different colors to indicate the status of different projects. It intuitively observes the current status of different projects. When you place the cursor over a small block, the main information of the Project is displayed. The status statistics of the build project are displayed on the right of the page to learn about the build overview. Several other gadgets provide RSS connections and more user-friendly page configuration tools.
Before introducing dashboard, we were familiar with the status of items in CC. CC divided the items into three categories: discontinued, inactive, and active ).

• Discontinued (STOP)Indicates that CC can find the log file for this project, but it is not found in the configuration file (config. XML. So CC won't build it, but you can see the historical information of the previous build of this project. To delete a project from CC, you only need to delete the log directory of the project. If the project name is "petclinic", the directory is $ {cruisecontor. Home}/logs/petclinic.
• Inactive)Indicates CC in the configuration file (config. XML), but no historical information about the project is found, that is, the log file of the project is not found in the CC log directory, or the log file is manually deleted. CC checks the new version of the project based on the configuration information and builds the project. After the first build is complete, CC generates logs and the project status changes to active.
• Active)CC indicates that the log file of the project can be found, and it can be found in the configuration file (config. XML. In this case, the project may be built successfully, failed, or in progress.

Dashboard has four tag pages: dashboard, builds, build details, and administatiorn.
3.1. dashboard
The status of all projects is displayed on the left of the dashboard tab page. Different color blocks indicate different build statuses.

• The Red Square indicates that the last build of the project failed.
• The green square indicates that the last build of the project was successful.
• The gray square indicates that the project may be inactive or discontinued.

In addition, you can view the statistics of all build projects on the right side of the page. Different icons and numbers indicate the number of projects in different States.

3.2. Builds
On the tab page, statistics on the status of all build projects are displayed in the middle left, links to different tools are displayed in the middle right, and all Project Build information is displayed in the list at the bottom of the page.

In each build information, click to view all builds. Click the icon to view all successful builds. If you set force build to true, there is a button on the right side of the list. Clicking this icon forces the project to be built without waiting for the next check, you do not have to wait until the version changes. Click the building icon on the builds page and dashboard page.

In addition, you can configure the RSS and JMX console by using a tool icon. For details about the operations, see section 1.2.6 of report management method.

3.3. Build details
This tab page lists the details of a Project Build, including recent project file modification records, build logs, automated test results, build warnings, and errors. If the build is successful, in the configuration file (config. the artifacts configured in XML is also displayed on the tab page named artifacts.
The list on the right is the list of all historical builds of the project. Click one of the builds to obtain the details of the build.

3.4. Administration
On this page, you can see the about and Configuration sub-tags.
In the about sub-tag, you can see the environment information used by CC, such as the CC version number, operating system, and JDK version.

In the administration subtab, you can see the contents of the CC Dashboard-config.xml file.