Is project still maintained ?

[whatthefrog]

Last release was more than 2 years ago ?

Last commit about ~17 months ago, May 2019 ?

[klafbang]

I'm not the maintainer and cannot speak for them, but somebody else (also not me) made a fork at https://github.com/javamachr/sonar-gitlab-plugin which has been updated to handle Sonar 8.2. It's not been updated for a while either, but has been working for me so far and also survived the upgrade to 8.5 I did today.

[idelin]

I'm not the maintainer and cannot speak for them, but somebody else (also not me) made a fork at https://github.com/javamachr/sonar-gitlab-plugin which has been updated to handle Sonar 8.2. It's not been updated for a while either, but has been working for me so far and also survived the upgrade to 8.5 I did today.

🤩thanks

[lucasoares]

@klafbang can you share know how are you configuring it for sonar > 7.7?

Examples of gitlab MR page of how the plugin is handling it are also welcome!

Since the preview mode doesn't exists at Sonar > 7.7 I'm not sure on how the plugin would be configured using sonar.analysis.mode=preview

Thanks!

[klafbang]

Sure, nothing too much, really.

I'm using maven; just configure:

	<properties>
		<sonar.host.url>...</sonar.host.url>
		<sonar.login>...</sonar.login>
	</properties>
...
				<plugin>
					<groupId>org.sonarsource.scanner.maven</groupId>
					<artifactId>sonar-maven-plugin</artifactId>
					<version>3.7.0.1746</version>
				</plugin>

From Gitlab CI, I launch with

    - mvn $MAVEN_CLI_OPTS install sonar:sonar -Dsonar.gitlab.project_id=$CI_PROJECT_PATH -Dsonar.gitlab.commit_sha=$CI_COMMIT_SHA -Dsonar.gitlab.ref_name=$CI_COMMIT_REF_NAME

(the split between properties and command line options are tailored for a shared parent project we use for several different actual projects)

In Sonar (8.5.1.38104 currently), configure Gitlab URL + Gitlab User Token. I've increased the timeout values and customized which issues to report, but everything else is default.

I'm not using it with MRs, but get comments on commits:

Developers get a mail from Gitlab if the quality gate is violated. I've configured quality gate + an instance default custom ruleset in Sonar so all projects get same checks by default; some projects override various settings using the pom.

[lucasoares]

Thanks!!

My problem is exactly with discussions and MRs.

I use detached pipelines (only for merge requests) and I use the merge_request_discussion feature to start discussions instead of just comments.

Using the plugin the external job stage with quality gate result is being created in another pipeline and not on my detached. This is overwriting the pipeline shown in the MR.

The discussion also are not working. If I go to gitlab to reply them, the gitlab UI bugs and no text area is shown.

I'm looking into the plugin code to check what I can do to fix this.

EDIT:

Appears that the API doesn't support external job for detached pipelines :(
Just created: https://gitlab.com/gitlab-org/gitlab/-/issues/300720

[lucasoares]

@javamachr could you open your fork to accept issues?

Let's take care of the project in your fork until the maintainer or its members see this issue.

I'd like to contribute =)

[javamachr]

@javamachr could you open your fork to accept issues?

I just enabled it - wasn't aware its disabled 🤦🏻‍♂️

[mars-dlx]

@lucasoares You can look on my fork. I also include some changes from https://github.com/javamachr/sonar-gitlab-plugin. My version for SonarQube < 7.9.x.

[lucasoares]

@Mar-Ser could you please provide PRs so we can use @javamachr fork instead? We already have few people there contributing with the plugin.

[mars-dlx]

@lucasoares

• https://github.com/javamachr/sonar-gitlab-plugin - SQ > 8 (preview mode deprecated)
• https://github.com/Mar-Ser/sonar-gitlab-plugin - SQ < 7.9.x (origin plugin + some changes from @javamachr)
• Origin repo - SQ < 7.9.x (but very weird Readme changes)

So, I don't understand, what kind PRs you want from me. My fork is almost the same. Just for the older SQ version.