-
-
Notifications
You must be signed in to change notification settings - Fork 283
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HtmlSummary doesn't work with Azure Pipelines #602
Comments
I would suggest that you go with option 4. Regarding the other options:
This could cause problem if you generate other formats as well.
Definitely "no". I try to keep the number of parameters as low as possible.
The behavior would then be different from the other summary reports. |
I have a very similar case where, due to the number of classes, generating the report takes a 3-5 minutes. However, generating the HtmlSummary takes only a few seconds. Option 4 does not work when I simultaneously use publishCodeCoverageResults: true. Option 2 or 3 would be very useful. |
@marcinsku |
@marcinsku I will publish a new release within the next days. |
That's great! Thank you for the quick response. |
New release 5.3.7 is now available. |
Describe the bug
Because of the size of our repo, when code coverage files are generated with
HtmlInline_AzurePipelines
, we run out of space on our hosted agent.HtmlSummary seemed like a good solution, but it generates a summary.html file, which is not picked up by the Azure Pipeline UI:
Some options:
summary.html
toindex.html
.HtmlSummary_AzurePipelines
.The text was updated successfully, but these errors were encountered: