Cobertura reporter breaks on 2.6.0

@tonerdo I noticed similar issue reported in https://github.com/tonerdo/coverlet/issues/295 I recently upgraded coverlet version from 2.3.1 to 2.6.0 (some of my team members upgraded from 2.5.0 to 2.6.0) and our Cobertura reporter started failing.

Below is the log:

[Cobertura] Publishing Cobertura coverage report...

[Cobertura] No coverage results were found using the pattern '**/TestResults/coverage.*.xml' relative to '/home/ec2-user/workspace/'.  Did you enter a pattern relative to the correct directory?  Did you generate the XML report(s) for Cobertura?

This is our jenkin pipeline step that is failing right now with 2.6.0:

step([$class             : 'CoberturaPublisher',
                      autoUpdateHealth   : false,
                      autoUpdateStability: false,
                      coberturaReportFile: '**/TestResults/coverage.*.xml',
                      failUnhealthy      : false,
                      failUnstable       : false,
                      maxNumberOfBuilds  : 0,
                      onlyStable         : false,
                      sourceEncoding     : 'ASCII',
                      zoomCoverageChart  : false])

Same reporter works fine with 2.3.1 and my team members reported worked until 2.5.0. Please can you look into this? If you need anything from my side please let me know.

[jpaskhay]

details of current failure specifically covered in https://github.com/tonerdo/coverlet/issues/295#issuecomment-473414110

[daveMueller]

Yes the cobertura plugin from jenkins expects a cobertura file that as a non empty source tag and relative paths in the filename attribute. This was changed to support Sourcelink in #260. In #614 I changed it back to support the jenkins plugin again and also support the Sourcelink feature. However if --use-source-link-switch is true, the jenkins plugin implementation is too limited and can’t display the reports. Nevertheless the ReportGenerator can display it (https://github.com/danielpalme/ReportGenerator/issues/180).