| Key: |
CIB-562
|
| Type: |
Improvement
|
| Status: |
Resolved
|
| Resolution: |
Fixed
|
| Priority: |
Major
|
| Assignee: |
jason
|
| Reporter: |
Jeremy Higgs
|
| Votes: |
0
|
| Watchers: |
1
|
|
If you were logged in you would be able to see more operations.
|
|
|
Pulse
Created: 14/Aug/06 06:19 AM
Updated: 19/Oct/06 10:47 AM
|
|
| Component/s: |
Notifications
|
| Affects Version/s: |
None
|
| Fix Version/s: |
1.2
|
|
|
It would be great to have more information in the Jabber build messages, as they do not have much information at the moment:
project <NAME>: build 32: failure
Instead, I would hope to see the following:
* Build URL
* Number of tests passed/failed (if applicable)
* Which stage the build failed (bootstrap? svn auth problems? build issue? test issue?)
* Changeset message (if triggered by an SCM change) / Manual trigger (Perhaps include a link to the SCM changeset in FishEye, etc, if that's implemented)
* Whether the build is the first failure, or one of a successive number of builds (e.g. "build n failed after prior success", "1 more test failed this time than build (n-1)")
* Which committer broke the build (if not a manual trigger)
This might be an example:
Build n(Link) of project <NAME> failed in stage "test".
2 out of 500 tests failed, (Link to test page) 1 more than the last build.(Link)
Triggered by commit from johndoe: "Fixing the build"
|
|
Description
|
It would be great to have more information in the Jabber build messages, as they do not have much information at the moment:
project <NAME>: build 32: failure
Instead, I would hope to see the following:
* Build URL
* Number of tests passed/failed (if applicable)
* Which stage the build failed (bootstrap? svn auth problems? build issue? test issue?)
* Changeset message (if triggered by an SCM change) / Manual trigger (Perhaps include a link to the SCM changeset in FishEye, etc, if that's implemented)
* Whether the build is the first failure, or one of a successive number of builds (e.g. "build n failed after prior success", "1 more test failed this time than build (n-1)")
* Which committer broke the build (if not a manual trigger)
This might be an example:
Build n(Link) of project <NAME> failed in stage "test".
2 out of 500 tests failed, (Link to test page) 1 more than the last build.(Link)
Triggered by commit from johndoe: "Fixing the build" |
Show » |
|
Increased information in Jabber build messages
It could even be fully customizable by exposing simple replacement tokens
such as ${link}, ${build}, ${errorMessage} etc.
A link to the Pulse summary for the Project is definitely missing at the moment.