-
-
Notifications
You must be signed in to change notification settings - Fork 432
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
Option to use relative file paths in xml report #948
Closed
kammala opened this issue
Feb 27, 2020
· 5 comments
· Fixed by CSCfi/oidc-client#35 or CSCfi/beacon-python#162
Closed
Option to use relative file paths in xml report #948
kammala opened this issue
Feb 27, 2020
· 5 comments
· Fixed by CSCfi/oidc-client#35 or CSCfi/beacon-python#162
Labels
Comments
inspired by discussion in #597 |
This seems very reasonable :) |
Same issue here :( CodeClimate outside of docker fails as the report is using absolute path. |
nedbat
added a commit
that referenced
this issue
Mar 15, 2020
As of f668d6f, using |
This is now available in coverage v5.0.4 |
This was referenced Mar 16, 2021
This was referenced May 29, 2021
This was referenced Jun 6, 2021
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
There is an option for
run
command to store only relative file paths. It is very useful while running your tests inside one environment(e.g. docker) and using results in another one(e.g. on Jenkins node). It is also common to generate cobertura report in the same environment you are running tests, but this report always includes absolute path for sources(I think, because of this line). This way it is impossible for tools like Jenkins Cobertura plugin or Sonarqube to find source files properly(Sonarqube either fails to parse coverage report at all or raises warning, for example).Describe the solution you'd like
json
reports use paths from.coverage
file and thus respect thisrelative_files
setting fromrun
section.It would be nice either to not canonicalize paths for sources or to have an option which will skip path normalization(this way it may be more backward compatible)
Describe alternatives you've considered
I tried to use
combine
and define sources in[path]
section of config but it ends up with absolute path in the end report anyway.The text was updated successfully, but these errors were encountered: