Closed ManfredSchenkIOSB closed 5 months ago
Hi @ManfredSchenkIOSB, which documentation are you referring to? For MR decoration, you need a token with API write access. For importing projects into SonarQube, a read_api
token is enough. So there are basically 2 tokens in the end. One for the MR decoration and one for importing projects.
As a side note: I doubt that the bug
label fits in this case, as this is not a plugin bug.
@xC0dex I agree with you that the bug
label doesn't fit here, but the input form only offered the Labels bug
or Report Security vulnerability
. So I chose bug
since security vulnerability
would have been a worse choice.
I would have chosen the label unclear documentation
if it had been offered to me.
In original documentation of the Sonarqube server only the read_api
token is mentioned. Meanwhile I found some statements where the requirement of the api
scope is explained. But I think the documentation could be more clear in this case.
But I think the documentation could be more clear in this case.
I see your point, the official documentation can be misleading. However, the documentation is not part of this project. Maybe to improve the docs in their project.
closing the issue. Perhaps this issue helps other who are faced with the same error message in the future.
Describe the bug MR decoration with gitlab is not working.
To Reproduce Steps to reproduce the behavior:
Follow the documentation how to setup MergeRequest decoration with Gitlab SelfManaged.
Especally the part where it is mentioned that the Access token only needs scope "read_api"
Expected behavior A clear and concise description of what you expected to happen.
Screenshots If applicable, add screenshots to help explain your problem.
Software Versions
Additional context
part of the logs mentioning that the scope of the access token is not sufficient to decorate the MR: