-
Notifications
You must be signed in to change notification settings - Fork 238
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
Since the Cobertura coverage-04.dtd document URL is http, sonar-scanner cannot format it #558
Comments
That is very subtle. I think it should probably always just use |
ksuther
added a commit
that referenced
this issue
May 27, 2024
…base/fix-558 Fix #558: cobertura.sourceforge.net should use https instead of http.
The change to https was good, but the url is still 404. I've found the correct url ( |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm scanning my iOS project with sonar-swift.sh using sonarqube.
slather coverage --input-format profdata --cobertura-xml --output-directory sonar-reports --workspace test.xcworkspace --scheme test test.xcodeproj
It gives Cobertura XML Output directly in my cobertura.xml output.
<?xml version="1.0"?><!DOCTYPE coverage SYSTEM "http://cobertura.sourceforge.net/xml/coverage-04.dtd">
But later when I run sonar-scanner
sonar-scanner -Dsonar.host.url=https://sonarqube.xxx.com/ -Dsonar.login=**** -Dsonar.projectKey=test -Dsonar.qualitygate.wait=true -Dsonar.qualitygate.timeout=600 --define sonar.projectVersion=19.2.0
It gives an error as an exception. I think "https://cobertura.sourceforge.net/xml/coverage-04.dtd" should be used here instead of "http://cobertura.sourceforge.net/xml/coverage-04.dtd"
Is there a parameter for https when creating cobertura.xml in slather?
because http://cobertura.sourceforge.net/xml/coverage-04.dtd is a 301 redirect.
The text was updated successfully, but these errors were encountered: