-
Notifications
You must be signed in to change notification settings - Fork 133
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
Source code is unavailable (Cobertura plugin 1.10) #103
Comments
I'm having the same issue |
@henryborchers - I know you just updated the plugin - is this new with the latest version, or were you having it before? |
@vitalykarasik - sorry for the slow response. Can you share the step from your Jenkinsfile that publishes the code coverage? Hopefully that should allow me to repro and fix |
@henryborchers - same request - can you share the step from your Jenkinsfile that publishes the coverage? |
@jeffpearce I'm actually trying out the new Jenkins Coverage Adapter for Cobertura so mine might be a little different. The xml file parses correctly but the generated report doesn't link to the source files |
Same issue for me |
@milos-u You need to click the name of sub-element to enter next level to see source files. You can see them below the chart you trying to click. |
I'm producing coverage report by coverage.py and use "Publish cobertura report".
I do have "Cobertura Coverage Report" , but couldn't not see Python sources.
Can please someone point to to the document or example or proper coverage.xml file?
I reviewed coverage.xml, and filenames seem be right - "/opt/mydir/mypackage/vitaly.py".
In the same time into "Coverage Breakdown by File" section of report I see this path without leading slash, i.e. "opt/mydir/mypackage/vitaly.py".
Seems to be different from #102 - I do have admin right.
TIA,
Vitaly
The text was updated successfully, but these errors were encountered: