Open alixwar opened 6 years ago
Hi, Gitlab member is reporter or developer ?
Is you sure to have the same error log with sonar.gitlab.failure_notification_mode = exit-code ? Because error in previous log is caused by commit-status only
Hi, the member is "master". Maybe the problem is the defaults in SonarQube. If they are somehow used instead of the parameters I'm sending, then that would explain a lot.
Is you sure to have the same error log with sonar.gitlab.failure_notification_mode = exit-code ? Because error in previous log is caused by commit-status only
With exit-code the build succeeds, but the specified user token should have all it needs for the other notification mode in my opinion.
In Gitlab (under Profile settings / Access Tokens) I have tried creating both a token with both scopes ("api", "read_user") set and only "api" with the same result. What is the requirement for the default notification mode?
Hi, For commit-status, you need a GitLab user who is at least a developer of the project. With this user create an api access token
Hi, I'm running version 2.1.0 of the plugin with Gitlab 10 (Enterprise Edition) and getting an error:
I have previously analyzed successfully against a Gitlab 8 instance (v3 syntax). In SonarQube I still have the defaults for v3 but I have overriden these properties (see below).
The Gitlab project has the following properties:
The build agent OS is linux and I am setting the following properties:
I have also tried setting
sonar.gitlab.failure_notification_mode=exit-code
but with the same result