-
-
Notifications
You must be signed in to change notification settings - Fork 530
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
Could not decorate Gitlab merge request. 'sonar.pullrequest.gitlab.instanceUrl' has not been set in scanner properties #201
Labels
Comments
Same issue with me here are the logs(ce.log):
sonarqube version: 8.2 please reply |
Hi all this work for me: |
PiekJ
added a commit
to PiekJ/sonarqube-community-branch-plugin
that referenced
this issue
Jul 23, 2020
Fixed setting the project id on sonarqube project pull decorate option when selecting GitLab. When project id is set use that instead of the sonarqube scanner property. Fixed always evaluating fetching sonarqube scanner property for instance url.
PiekJ
added a commit
to PiekJ/sonarqube-community-branch-plugin
that referenced
this issue
Jul 23, 2020
Fixed setting the project id on sonarqube project pull decorate option when selecting GitLab. When project id is set use that instead of the sonarqube scanner property. Fixed always evaluating fetching sonarqube scanner property for instance url.
PiekJ
added a commit
to PiekJ/sonarqube-community-branch-plugin
that referenced
this issue
Jul 23, 2020
Fixed setting the project id on sonarqube project pull decorate option when selecting GitLab. When project id is set use that instead of the sonarqube scanner property. Fixed always evaluating fetching sonarqube scanner property for instance url.
PiekJ
added a commit
to PiekJ/sonarqube-community-branch-plugin
that referenced
this issue
Jul 23, 2020
Fixed setting the project id on sonarqube project pull decorate option when selecting GitLab. When project id is set use that instead of the sonarqube scanner property. Fixed always evaluating fetching sonarqube scanner property for instance url.
PiekJ
added a commit
to PiekJ/sonarqube-community-branch-plugin
that referenced
this issue
Jul 25, 2020
Fixed setting the project id on sonarqube project pull decorate option when selecting GitLab. When project id is set use that instead of the sonarqube scanner property. Fixed always evaluating fetching sonarqube scanner property for instance url.
PiekJ
added a commit
to PiekJ/sonarqube-community-branch-plugin
that referenced
this issue
Jul 27, 2020
Fixed setting the project id on sonarqube project pull decorate option when selecting GitLab. When project id is set use that instead of the sonarqube scanner property. Fixed always evaluating fetching sonarqube scanner property for instance url.
PiekJ
added a commit
to PiekJ/sonarqube-community-branch-plugin
that referenced
this issue
Aug 3, 2020
Fixed setting the project id on sonarqube project pull decorate option when selecting GitLab. When project id is set use that instead of the sonarqube scanner property. Fixed always evaluating fetching sonarqube scanner property for instance url.
mc1arke
pushed a commit
that referenced
this issue
Aug 3, 2020
SonarQube 8.2 introduced the ability to set the repository ID through the front-end for use when decorating a Gitlab Merge Request, although this was missed from the plugin when implementing the appropriate interfaces. This change therefore introduces the required implementation, and additional only attempts to resolve the server ID from scanner properties when the ID has not been set through the front-end,
Released in 1.5.0 of the plugin |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Describe the bug
I am getting this when I use those settings for VS C# solution. i set instanceUrl but keep getting that error.
To Reproduce
Steps to reproduce the behavior:
The text was updated successfully, but these errors were encountered: