infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Fabrice Bellingard (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (INFRA-17867) CLONE - Install Sonarqube Github plugin
Date Sun, 03 Mar 2019 13:59:00 GMT

    [ https://issues.apache.org/jira/browse/INFRA-17867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16782735#comment-16782735
] 

Fabrice Bellingard edited comment on INFRA-17867 at 3/3/19 1:58 PM:
--------------------------------------------------------------------

Looking at [~rombert]'s original request (https://lists.apache.org/thread.html/46ed5b81cb17303387442144d44eb3080b8e0c45c28eee99ca4520d8@%3Cbuilds.apache.org%3E),
the only way to have PRs decorated on GitHub with an "old" 5.6 SonarQube is to install this
deprecated plugin.

However, I agree with you [~gmcdonald] that having to install a deprecated plugin is a sign
that something's not going well. And this something is: the Apache instance runs a SonarQube
5.6 which is an outdated LTS version that SonarSource is not supporting any longer. From there,
because I fully understand that the Apache teams would love to have their PRs analyzed and
decorated on GitHub, there are 2 options:
* Wait for the next LTS (ETA: June 2019) and ask SonarSource to get a license for the SonarQube
Developer Edition so that you can upgrade the Apache instance and enable the built-in feature.
* Progressively help Apache teams to move to SonarCloud (https://sonarcloud.io) which is 100%
free for OSS communities and which offers out-of-the-box PR analysis and decoration. SonarCloud
is SonarSource cloud service for code analysis, it offers almost the same features as SonarQube
and you don't have to manage the instance - which I believe can be a good relief for the Infra
team.

If you go for option #2, I could definitely help since SonarCloud is the product I'm leading
at SonarSource.



was (Author: bellingard):
Looking at [~rombert]'s original request (https://lists.apache.org/thread.html/46ed5b81cb17303387442144d44eb3080b8e0c45c28eee99ca4520d8@%3Cbuilds.apache.org%3E),
the only way to have PRs decorated on GitHub with an "old" 5.6 SonarQube is to install this
deprecated plugin.

However, I agree with you [~gmcdonald] that having to install a deprecated plugin is a sign
that something's not going well. And this something is: the Apache instance runs a SonarQube
5.6 which is an outdated LTS version that SonarSource is not supporting any longer. From there,
because I fully understand that the Apache teams would love to have their PRs analyzed and
decorated on GitHub, there are 2 options:
# Wait for the next LTS (ETA: June 2019) and ask SonarSource to get a license for the SonarQube
Developer Edition so that you can upgrade the Apache instance and enable the built-in feature.
# Progressively help Apache teams to move to SonarCloud (https://sonarcloud.io) which is 100%
free for OSS communities and which offers out-of-the-box PR analysis and decoration. SonarCloud
is SonarSource cloud service for code analysis, it offers almost the same features as SonarQube
and you don't have to manage the instance - which I believe can be a good relief for the Infra
team.

If you go for option #2, I could definitely help since SonarCloud is the product I'm leading
at SonarSource.


> CLONE - Install Sonarqube Github plugin
> ---------------------------------------
>
>                 Key: INFRA-17867
>                 URL: https://issues.apache.org/jira/browse/INFRA-17867
>             Project: Infrastructure
>          Issue Type: New Feature
>          Components: Analysis, Jenkins
>         Environment: builds.apache.org/analysis
>            Reporter: Robert Munteanu
>            Assignee: Gavin
>            Priority: Major
>
> https://docs.sonarqube.org/display/PLUG/GitHub+Plugin 
> Install + Document



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message