| Key: |
CIB-1092
|
| Type: |
Improvement
|
| Status: |
Resolved
|
| Resolution: |
Fixed
|
| Priority: |
Minor
|
| Assignee: |
Unassigned
|
| Reporter: |
Henrik Goldman
|
| Votes: |
0
|
| Watchers: |
1
|
|
If you were logged in you would be able to see more operations.
|
|
|
Pulse
Created: 19/May/07 09:40 PM
Updated: 20/May/07 11:41 PM
|
|
| Component/s: |
Notifications
|
| Affects Version/s: |
1.2.x
|
| Fix Version/s: |
1.2.27
|
|
|
It would be really good if you could see the start time and end time for a build within emails.
Currently it doesn't show this. E.g. I have some test cases which fails in the middle of the night because the code which fails deals with date/time handling. For this reason it would be useful to know the start time and duration to be able to recreate the problem.
|
|
Description
|
It would be really good if you could see the start time and end time for a build within emails.
Currently it doesn't show this. E.g. I have some test cases which fails in the middle of the night because the code which fails deals with date/time handling. For this reason it would be useful to know the start time and duration to be able to recreate the problem. |
Show » |
|
Start and end time of a build
This is a perfect example of where the pulse email templates can be used, although for the data you are interested in, I will need to make a slight adjustment in the build that will be available later today.
What I recommend you try is the following:
1) have a quick read through http://confluence.zutubi.com/display/pulse0102/Subscription+Templates
2) go to PULSE_DATA/config/templates/project-builds/
3) rename custom-ext-email.ftl.example to custom-ext-email.ftl
4) add the following:
Start : ${result.stamps.prettyStartDate}
Finish : ${result.stamps.prettyEndDate}
These two variables will be available in 1.2.27 and will print out the start and end dates for the build.
Cheers,
-Daniel