Feature: New out-format gometalinter

[timme04]

Hi,
thanks for your awesome work on golangci-lint.

For using golangci-lint in ci/cd pipelines together with our well established Sonarqube, it would be helpful, if golangci-lint could print a gometalinter compatible format.

The gometalinter-format is one of Sonarqubes supported formats when importing external issues. See https://docs.sonarqube.org/latest/analysis/external-issues/

Today I'm using a perl regular expression to reformat golangci's output to the gometalinter format, which sonarqube understands.
golangci-lint run --deadline=30m --out-format=line-number | perl -pe 's/(?<file>[^:]+):(?<line>\d+):(?<col>\d*): (?<message>.*)\((?<linter>[^\(]*)\)/$+{file}:$+{line}:$+{col}:error:$+{message}($+{linter})/g'
This is far from optimal, but works.

I could provide a pull request.
What do you think?

[ryancurrah]

Sonarqbue addressed this issue in July they have not updated the documentation to reflect it. Basically use the checkstyle out-format and the configuration syntax below for sonar-scanner.

sonar.go.golangci-lint.reportPaths=golangci-lint-report.xml

https://github.com/SonarSource/slang/blob/d75b521ab3f7b511d9735a5c7b13db3392cae4e9/sonar-go-plugin/src/main/java/org/sonar/go/externalreport/GolangCILintReportSensor.java#L31-L52

[jirfag]

hi, if you can use checkstyle output - it's not needed

[tpounds]

A similar request was made in #228. As @jirfag mentioned several additional output formats have been added that should fulfill the requirements of this request.

• Checkstyle (Checkstyle support #95)
• JUnit (junit-xml output #557)
• Code Climate (Add code-climate output format #386)