
| Key: |
BCOV-19
|
| Type: |
Improvement
|
| Status: |
Resolved
|
| Resolution: |
Fixed
|
| Priority: |
Major
|
| Assignee: |
Dan Grabowski
|
| Reporter: |
mark@atlassian.com
|
| Votes: |
0
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
|
|
|
| Component/s: |
None
|
| Affects Version/s: |
1.0.1
|
| Fix Version/s: |
1.0.2
|
|
|
File Attachments:
|
None
|
|
Image Attachments:
|
|
|
Issue Links:
|
Reference
|
|
This issue relates to:
|
|
|
BCOV-25 Allow users experiencing issues to easily gather and submit debug information
|
|
|
|
|
|
|
|
|
It'd be nice if, when no coverage files can be found, the plugin can log warnings to the ErrorHandler so that the user gets some feedback when they've misconfigured.
|
|
Description
|
It'd be nice if, when no coverage files can be found, the plugin can log warnings to the ErrorHandler so that the user gets some feedback when they've misconfigured. |
Show » |
|
Issues encountered while parsing the coverage report files, including not finding a report file, are now added to the build results as error messages. These don't fail the build, but do show up on the build summary tab as build errors.
Is this right way to go about it, or would it be cleaner to use the ErrorHandler?