Overview tab
| There is a Run button and a build history interface in the top right corner of the page. Click the Run button to re-run the current build configuration. Click the guillemets (angle quotes) on the build history interface to navigate to Build Results pages of the previous and next builds (identified with their build state and number), or click the All history link to view the build history tab of the build configuration home page. |
 |
The top part of the tab is color coded (green if the build passed all the test, red if it failed, and blue if it is still running).
Finished builds
| Item |
Description
|
Result
|
Shows the build result message and status icon.
|
Time
|
Shows the build's start time and the duration it took to build.
|
| Agent |
Link to the agent that ran the build. Clicking this link opens the Agent Details page.
|
| Triggered |
Shows what triggered the build, and when it happened.
|
| Pin status |
Use Pin/Unpin link to toggle pinned status of the build result.
|
| Tags |
View any build tags that have been assigned to the build, and edit tags.
|
Running builds
| Item |
Description
|
Hanging build notification
|
If a build is probably hanging, the following notification appears on top of the Overview tab: |
Started
|
Shows build start time and status icon. Use Stop build link to kill the entire build process, in case something goes wrong. To investigate the issue, use Thread dump link. |
| Time left |
Shows estimated time left to build completion (passed and estimated total time in brackets)
|
Agent
|
Link to the agent that is running the build. Clicking this link opens the Agent Details page.
|
Triggered
|
Shows what triggered the build, and when it happened.
|
| Responsible |
This field is available for the failing builds. Click the Take responsibility link, if you consider yourself responsible for the problems in this build. |
| Thread dump |
Click the View thread dump link to view the process tree of the running build, and thread dumps of each Java or .Net process in a separate frame. If the process is not Java or .Net, its command line is retrieved. The possibility to view thread dump is supported for the following platforms:
- Windows, with JDK 1.3 and higher
- Windows, with JDK 1.6 and higher, using jstack utility
- Non-Windows, with JDK 1.5 and higher, using jstack utility
|
| Running step |
Shows the current step of the build procedure.
|
 | If another build of this same build configuration is concurrently running, a small window will appear with the following information:
- The build results of that build linking to the build results page;
- A changes link with a drop-down list of changes included in that build;
- The build number, time of start, and a link to the agent it is running on.
|
Either of the above sections is followed by an overview of tests, code coverage and/or duplicates search if they are part of the build configuration. Failed tests provide links to where they can be viewed in the web UI or the IDE. Failed tests that have been fixed will appear as struck-through text and will list the build in which the fix first appeared.
The overview of tests includes information about the failed, ignored and passed tests:
Expand the failed tests node to see the details:
See also: