[ https://issues.jenkins-ci.org/browse/JENKINS-13889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163195#comment-163195 ]
cangove commented on JENKINS-13889: ----------------------------------- Thanks! That makes sense. So I can prep the proper report and possible fix for coverage, do the paths in <sources> need to be absolute or can they be relative to the coverage report? > Cobertura plugin is not able to find code from python coverage > -------------------------------------------------------------- > > Key: JENKINS-13889 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13889 > Project: Jenkins > Issue Type: Bug > Components: cobertura > Affects Versions: current > Reporter: cangove > Assignee: stephenconnolly > Attachments: coverage.xml, coverage_by_cobertura.xml > > > Our repository has all src code under /src. So when running tests and > coverage the coverage.xml file is generated in $WORKSPACE/src. In the job > config I specify **/coverage.xml in the location. Th eCobertura plugin finds > the coverage report but states: > Source code is unavailable. Some possible reasons are: > This is not the most recent build (to save on disk space, this plugin only > keeps the most recent builds source code). > Cobertura found the source code but did not provide enough information to > locate the source code. > Cobertura could not find the source code, so this plugin has no hope of > finding it. > I believe this is due to the fact that coverage.xml records the relative path > to the files. As this file is in $WORKSPACE/src I would expect it to find the > files in $WORKSPACE/src/<relative path>, but I susepct it's omitting the > 'src' directory. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira