[Cruisecontrol] Build dashboard

What is a cruisecontrol dashborad?

Cruisecontrol dashboard is a powerful tool to help you visualize the status of your projects. The build results of previous projects are highlighted in color so that you can get the build results of your projects immediately. Builds results are icons used to represent the status of the current project to display more directly (such as pause, queue, and building ).

When you place your mouse on the Color Block used to represent the project builds, you can see the project and many information, such as the project name, the server where the project runs and the time when the last build occurred.

 

The meaning of color blocks:

Normally, the square has a green or red background color. Red indicates that the last build failed, and Green indicates that the last build succeeded. The longer the build keeps it, the deeper its color. In special cases, if the previous build of a project succeeds, the current build is green. If the previous build of a project fails, the current build is orange.

The following are some instances that you may see and there are more combinations, but you should be able to deduce them from the example below,

The last successful build of a project exceeds 24 hours, and the queue is currently waiting for build;

Indicates that the last build of a project in the past 24 years is successful;

The build of a project fails and exceeds 24 hours;

Indicates that the last build of a project in the past 24 hours failed and is currently in the paused state;

Indicates that the previous build of a project is successful and is currently in the build state;

Indicates that a project is inactive or stopped;

 

The following is a list of actions you can perform: access the RSS feed of Project Build and access the XML feed using cctray or cruisecontrol JMX console.

 

2. Dashboard build page

This is the build page, which allows you to view the status of each project build and perform the following actions on the project:

View All successful builds;

View All builds;

Force start a build;

Access the build RSS feed and cruisecontrol JMX console of each project;

 

Details page of dashborad build

1) Build details page

The build details page contains the Project Build information, such as the last successful build, build number, build interval, and the last 25 builds.

 

2) Details page of the current build

This is the details page of the current build project. The build output is displayed in real time.

 

Dashboard administration page

On this page, you can view detailed information about the dashboard configuration, such as the build, operating jvm OS, and JVM version information. Click the configuration sub-tab to view the specific information of the configuration and configuration from where the dashboard is read.

 

Limits on dashboard

* If you have removed the log file of the project, dashborad cannot automatically discover and mark the project as inactive. You need a refresh page. If you delete the log folder of the project, cruisecontrol does not re-create it and you know that you restart cruisecontrol.

* If you remove a project from the config. xml configuration file of cruisecontrol, dashborad cannot be automatically found and indicates that the project is aborted. You need a refresh page.

* Although build loop can automatically apply modifications to the config. xml configuration file, dashborad cannot get modifications to the dashborad-config.xml configuration file. You need to restart dashborad to make the modification take effect.

 

Configuration of dashborad

You can configure dashborad in the following three ways:

* Web. xml of J2EE server. This method is not in favor;

* Dashborad-config.xml is recommended for configuration of dashborad. The default dashbord-config.xml is published along with cruisecontrol and is located in the same location as config. xml used to configure build loop.

* You can use system properties to override the configuration file settings;

 

System attributes:

The administrator can pass system attributes through the cruisecontrol. sh/cruisecontrol. bat or Web Container STARTUP script.

Property	Value	Default Value	Description
Cc. config. forcebuild	Enabled/disabled	Enabled	Whether the user can forcibly start build from the GUI
Cc. logdir	String	Logs	Specifies the full directory of the log of the cruisecontrol.
Cc. Artifacts	String	Artifacts	Specifies the full path of the build binary/master.
Dashboard. config	String	Dashboard-config.xml	Used to specify the path of the dashborad configuration file

 

Dashborad configuration file Dashborad-config.xml:

<Buildloop> tag is used to specify the logsdir and artifactsdir attributes related to the build loop of cruisecontrol.

<Features> the tag contains the attribute allforcebuild of the custom dashborad.

<Trackingtool> A tag contains the projectname, baseurl, and keywords attributes. It is used to create a link to submit annotations for the project management tool. Your projects can have zero or one <trackingtool> tag. Dashborad parses and submits messages to find the story number behind the specified keyword, and then uses the specified baseurl and story number to generate links. For example, if you submit the source code and the message is "I Fixed bug #425" and define <trackingtool> like <trackingtool projectname = "cc" baseurl = "http: // mingle05/projects/CCEE/CARDS/"KEYWORDS =" #, build "/>, dashborad will generate a link for your submitted message" <a href = http: // mingle05/projects/CCEE/CARDS/425> I Fixed bug #425 </a> ".

<Subtabs> A tag is used to specify the widget plugin for the build detail page. You can have zero or one subtabs tags. One subtabs can contain multiple subtab tags.

 

Complete!