Closed pedromauriciocosta closed 7 years ago
I am not aware of any reports.
Can you provide debug logs? (Please remove http credentials)
I'm seeing this as well, it's because api/resources has been removed in 6.3: https://sonarqube.com/web_api/api/resources
Excerpt from log:
GET /sonar/api/resources?resource=XXXXX&metrics=line_coverage&format=json HTTP/1.1
...
Response DefaultHttpResponse(decodeResult: success, version: HTTP/1.1) HTTP/1.1 404
So without the coverage feature everything works? This is unfortunate... The other API has only been introduced in 5.4, so it is not available in 5.2 LTS.
sonar-stash can support both API, why not?
I was mistaken. 5.6 is the LTS. As the plugin will only support 5.6 anyways this will be migrated to the new API.
This will also have to wait until the coverage part is split into its own plugin. Currently the sonar ws client needs same maven trickery to work and I'd like to keep this complexity out of the sonar-stash plugin.
Thanks for that. Any idea when could we have a working version?
I just want to install the plugin... So now I'm confused what is working and what is broken. The original post says that issues are not posted, but later on you say that coverage is the problem. Currently I'm not so much interested in the coverage feature as this is already solved for me in our Jenkins pipeline. I rather want that issues are commented on the PR.
@olafgeibig Currently the coverage feature is broken on SonarQube 6.3. The rest should work.
Maybe this is the same problem: https://github.com/AmadeusITGroup/sonar-stash/issues/120
@michalmikee I think you're right - the line_coverage issue I was also seeing in the logs might have been a red-herring
I just tested PR #127 and this also solved the issue for me - I'm now seeing issues showing up in PRs 😄
Any ETA on releasing 1.3.0? I built with PR #127 as well and finally things work properly.
I can confirm this works properly in 6.3!
I had the plugin working fine with SonarQube 6.2. But once I updated to 6.3 it stopped posting any issues. Has anyone encountered this problem?