| Key: |
CIB-1032
|
| Type: |
Improvement
|
| Status: |
Resolved
|
| Resolution: |
Fixed
|
| Priority: |
Minor
|
| Assignee: |
jason
|
| Reporter: |
Mark Melvin
|
| Votes: |
0
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
|
Pulse
Created: 27/Mar/07 07:07 PM
Updated: 18/Sep/08 09:03 PM
|
|
| Component/s: |
None
|
| Affects Version/s: |
1.2.20
|
| Fix Version/s: |
2.0.11
|
|
|
Issue Links:
|
Related
|
|
|
|
This issue is related to:
|
|
CIB-740
Capture more information from post bu...
|
|
|
|
|
|
|
It would be nice if you could capture the output of post-build actions to figure otu why things are failing and have that information available on the build results page for a project. Currently the only way I can see to determine what is blowing up the build in a post-build "run executable" type action is to check the wrapper.log file in your server's log directory.
|
|
Description
|
It would be nice if you could capture the output of post-build actions to figure otu why things are failing and have that information available on the build results page for a project. Currently the only way I can see to determine what is blowing up the build in a post-build "run executable" type action is to check the wrapper.log file in your server's log directory. |
Show » |
|
Ability to capture output of post-build action scripts
Agreed, the amount of information coming out of post build actions at the moment is very limited.
Our plan with this (2.x) is to make post build actions similar to standard recipes, so all of the functionality available during a build (reporting, analysis etc etc) will also be available to post build actions. This will require a fair chunk of effort, and so is currently scheduled for 2.x.
As for debugging, another option is to pipe the output from the post build executable to a file. For example, specify the exe as
post-build-action.sh > /var/tmp/post-build-action-output.txt
Hope this helps.