Use cruisecontrol to monitor your project-cruisecontrol step by step (4)

Now, we have established a continuous Integration Server for our project. Let's take a look at what cruisecontrol is saying to you.

I. project status

First, cruisecontrol divides the project into three types: discontinued, inactive, and active.

If a project is discontinued, cruisecontrol can find the log file of the project, but it does not exist in the configuration file (config. XML. So cruisecontrol won't build it, but you can see the history information of the previous build of this project. To delete a project from cruisecontrol, you only need to delete the log directory of the project. If the project name is "vcdstore", the directory is $ {cruisecontor. Home}/logs/vcdstore.

If a project is inactive, it indicates that cruisecontrol is in the configuration file (config. XML), but no historical information about the project is found, that is, there is no log file for the project in the log directory of cruisecontrol, or the log file is manually deleted. Cruisecontrol checks the new version and builds the project based on the configuration information. After the first build is complete, cruisecontrol will generate the log, and the project status will change to active.

If a project is active, it indicates that the log file of the project can be found in the configuration file (config. XML. In this case, the project may be built successfully, failed, or in progress.

Ii. dashboard

You can access the dashboard through http: // localhost: 8080/dashboard.

Dashboard has four main pages: dashboard, builds, build details, and administatiorn.

(1) dashboard

You can view the status of all projects on the dashboard. 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.

When you place the cursor over a small square, the main information of the Project is displayed. Click the small square to go to the build details page.

(2) builds

On the builds page, you can view the status of all projects in the form of a list. Click each list to go to the build details page.

If you set forcebuild to true, there is a button on the right side of the list, you can force the project to be built without waiting until the next check, or wait until there is a version change.

(3) Build details

This page lists the details of a build of the project, including the changes compared with the previous build, test results, and detailed log output. If the build is successful, in the configuration file (config. the artifacts configured in XML is also displayed on the tab named artifiacts.

The list on the right is the list of all builds of the project. Click a build to obtain the details of the build.

(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 the cruisecontrol, such as the version number, operating system, and JDK version of The cruisecontrol.

In the administration subtab, you can see the contents of the cruisecontrol Dashboard-config.xml file. In this version, modification is not supported, and the "add project" button is also removed.

Iii. cruisecontrol reporting

You can also access the old reporting of cruisecontrol through http: // localhost: 8080.

Click the project name to view details.

Iv. cruisecontrol JMX Console

You can also access the JMX console of cruisecontrol through the http: // localhost: 8000/link.

On the console, click the project name (such as connectfour) to modify the project configuration and pause/resume the project building.

TIPS:

(1) The above links are based on the default configuration of cruisecontrol.

(2) in the subsequent articles, we will introduce how to use build grid to expand our cruisecontrol build capabilities.