Introduction
New in 2.0, the entire pulse™ web interface now uses a predictable, readable URL scheme. This allows you to quickly and easily lookup and link to various pages and resources available through pulse™. It also supports permanent links to moving targets like the latest build, or the artifacts for the latest successful build.
Dashboard Section
| URL |
Description |
| /dashboard/home/ |
Your personal, configurable home page. |
| /dashboard/my/<build>/ |
Maps to a personal build, see below for possible <build> values and nested paths. |
| /dashboard/preferences/ |
Your pulse™ preferences, including subscriptions. |
Browse Section
| URL |
Description |
| /browse/ |
The browse view, which shows the latest status for all projects. |
| /browse/projects/ |
As above. |
| /browse/projects/<project>/ |
The home page for the specified project. |
| /browse/projects/<project>/home/ |
As above. |
| /browse/projects/<project>/reports/ |
The reports page for the specified project. |
| /browse/projects/<project>/history/(<page number>/)? |
The build history page for the specified project. An optional zero-based page index may be given. |
| /browse/projects/<project>/log/ |
The log view for the specified project. |
| /browse/projects/<project>/builds/<build>/ |
Maps to a project build, see below for possible <build> values and nested paths. |
Examples
To view the homepage of a project called "sample", you would use:
If the name of the project had a space in it, such as "sample project", you may need to encode that space as shown in the following example:
Server Section
| URL |
Description |
| /server/activity/ |
The server activity tab, which includes the build queues. |
| /server/messages/(<page number>/)? |
The server log messages tab, with an optional zero-based page index. |
| /server/info/ |
The server info tab. |
Agents Section
| URL |
Description |
| /agents/<agent>/ |
The specified agent's status tab. |
| /agents/<agent>/status/ |
As above. |
| /agents/<agent>/messages/(<page number>/)? |
The log messages tab for the specified agent, with an optional zero-based page index. |
| /agents/<agent>/info/ |
The specified agent's info tab. |
Examples
To view the second page of the recent log messages for an "master", you would use:
If the name of the agent had a space in it, such as "my agent", you may need to encode that space as shown in the following example:
Builds
Personal and project builds are reachable via the dashboard and browse sections respectively, as shown above. To specify a build, you can substitute the element <build> with either the build number (known in the UI as the build id), or one of the following virtual build identifiers:
| VID |
Description |
| latest |
The most recent build for the project or user. |
| success |
The most recent successful, completed build for the project or user. |
| broken |
The most recent failed, completed build for the project or user. |
Following the <build> element, various URLs are supported:
| URL |
Description |
| summary/ |
The summary tab for the build. |
| details/ |
The detailed view for the build. |
| details/<stage>/ |
The detailed view for the build, with the given stage selected. |
| details/<stage>/<command>/ |
The detailed view for the build, with the given command in the given stage selected. |
| changes/(sinceBuild/<number>)?/ |
The changes tab for the build, optionally specifying a build to show the changes since. |
| tests/ |
The tests tab for the build. |
| tests/<stage>/ |
The tests tab for the build, with tests from the given stage displayed. |
| tests/<stage>/(<suite element>/)* |
The tests tab for the build, with tests from the given suite in the given stage displayed. |
| file/ |
The pulse file tab for the build. |
| file/raw/true/ |
Downloads the raw pulse file for the build. |
| artifacts/ |
The artifacts tab for the build. |
| artifacts/<stage>/ |
The artifacts tab for the build, with the given stage selected. |
| artifacts/<stage>/<command>/ |
The artifacts tab for the build, with the given stage selected. |
| artifacts/<stage>/<command>/<artifact>/ |
For HTML report artifacts (directory artifacts with index files), shows the report. |
| artifacts/<stage>/<command>/<artifact>/(<path element>/)* |
For plain text files, shows a decorated view of the artifact file at the given path. |
| downloads/<stage>/<command>/<artifact>/(<path element>/)* |
Downloads the raw artifact file at the given path. |
| wc/ |
The working copy tab for the build. |
| log/ |
The tail view for the build log. |
| log/raw/true/ |
Downloads the raw log for the build. |
| logs/<stage>/ |
The tail view for the recipe log from the specified stage. |
| logs/<stage>/raw/true/ |
Downloads the raw recipe log for the given stage. |
Examples
To view the home page of the latest build for "sample" project, you would use:
To view build number 23 for the "sample" project, you would use:
To see the decorated view the latest output artifact produced by the "build" command in the "default" stage for the "sample" project:
To download the latest known good "package.tgz" produced in the "packages" artifact by the "dist" command in the "default" stage for the "sample" project:
To view an HTML JUnit report from the latest broken build, captures as the "junit" artifact by the "test" command in the "default" stage for the "sample" project:
