[GitHub Plugin] What is the future of the GitHub Plugin?

157 views
Skip to first unread message

msz...@wikia-inc.com

unread,
Jan 9, 2018, 1:08:27 PM1/9/18
to SonarQube
Hello,

I'd like to request some clarification regarding the future of the GitHub Plugin. Information on https://github.com/SonarSource/sonar-github/pull/30 and https://jira.sonarsource.com/browse/MMF-989 seem to indicate that most of the feature set provided by this plugin will be incorporated into the new Branch Plugin available as part of commercial SonarQube editions. Does this mean that the GitHub Plugin will cease development/be retired, or is its development simply on hold while the new alternative is being worked on?

Thank you in advance.

G. Ann Campbell

unread,
Jan 10, 2018, 3:13:39 PM1/10/18
to SonarQube
Hi,

Our intent for this plugin is to shelve it. As you noted, all the functionality it offers will be not just replaced but far outstripped by what is currently being added to the branch analysis functionality. 


Ann

msz...@wikia-inc.com

unread,
Jan 10, 2018, 3:15:35 PM1/10/18
to SonarQube
Hey Ann,

Thank you very much for the clarification! Does this mean that the plugin might not be kept compatible with future versions of SonarQube?

G. Ann Campbell

unread,
Jan 10, 2018, 3:53:04 PM1/10/18
to msz...@wikia-inc.com, SonarQube
Hi,

It pretty much guarantees it will not.


Ann



---
G. Ann Campbell | SonarSource
Product Manager
@GAnnCampbell

--
You received this message because you are subscribed to a topic in the Google Groups "SonarQube" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/sonarqube/tdUtFb2Bsgc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to sonarqube+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sonarqube/f367bad1-b779-437e-9c07-7b02c9e63ced%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

Petr Vilčinský

unread,
Jan 12, 2018, 1:07:41 PM1/12/18
to SonarQube
Hi,

is there any plan to check pull request before they are merged?
Because with GitHub plugin we are able to detect new defects and fix them before they are merged.

Thanks,
It is sad that the free version won't have basic functions.
I am not sure if that is good.

Dne středa 10. ledna 2018 21:53:04 UTC+1 G. Ann Campbell napsal(a):
Hi,

It pretty much guarantees it will not.


Ann



---
G. Ann Campbell | SonarSource
Product Manager
@GAnnCampbell

On Wed, Jan 10, 2018 at 3:15 PM, <msz...@wikia-inc.com> wrote:
Hey Ann,

Thank you very much for the clarification! Does this mean that the plugin might not be kept compatible with future versions of SonarQube?


On Wednesday, January 10, 2018 at 9:13:39 PM UTC+1, G. Ann Campbell wrote:
Hi,

Our intent for this plugin is to shelve it. As you noted, all the functionality it offers will be not just replaced but far outstripped by what is currently being added to the branch analysis functionality. 


Ann

On Tuesday, 9 January 2018 13:08:27 UTC-5, msz...@wikia-inc.com wrote:
Hello,

I'd like to request some clarification regarding the future of the GitHub Plugin. Information on https://github.com/SonarSource/sonar-github/pull/30 and https://jira.sonarsource.com/browse/MMF-989 seem to indicate that most of the feature set provided by this plugin will be incorporated into the new Branch Plugin available as part of commercial SonarQube editions. Does this mean that the GitHub Plugin will cease development/be retired, or is its development simply on hold while the new alternative is being worked on?

Thank you in advance.

--
You received this message because you are subscribed to a topic in the Google Groups "SonarQube" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/sonarqube/tdUtFb2Bsgc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to sonarqube+...@googlegroups.com.

G. Ann Campbell

unread,
Jan 15, 2018, 4:33:35 AM1/15/18
to SonarQube
Hi,

The Branch Analysis functionality will include PR analysis very soon.


Ann

nicolas.a...@mulesoft.com

unread,
Jan 17, 2018, 5:49:18 PM1/17/18
to SonarQube
As far as I know, the Branch analysis is just an enterprise feature, so what I'm hearing is that the team is deprecating open source functionality to favor enterprise model, is that correct?

G. Ann Campbell

unread,
Jan 18, 2018, 3:03:20 AM1/18/18
to nicolas.a...@mulesoft.com, SonarQube
Hi,

Since we have a commercial offering named "Enterprise Edition", I need to quibble that branch analysis is part of Developer Edition. But yes, it is a commercial feature.


Ann



---
G. Ann Campbell | SonarSource
Product Manager
@GAnnCampbell

To unsubscribe from this group and all its topics, send an email to sonarqube+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sonarqube/41ebdf5e-4f65-49c8-8d9d-940e3ab7e7fb%40googlegroups.com.

a.von...@gmail.com

unread,
Feb 6, 2018, 2:40:50 AM2/6/18
to SonarQube
Hi Ann,

could you please provide some details on when this soon(TM) will be? I'm in a bind right now, cause I made management buy us a Developer Edition license for branch analysis, since our workflow broke with 6.7 due to deprecated preview analysis mode. Unfortunately though, the branch analysis does not play well with the GitHub plugin:
* If I want branch analysis, I have to run analysis without sonar.analysis.mode=preview.
* If I want GitHub plugin to work and post comments on our GHE instance, I have to run analysis in preview mode.

So it seems right now I can have either a "preview" report via the branch analysis plugin *within SonarQube only*, or have the GitHub plugin post comments on the pull-request, but not a combination of the two. At least unless I run the analysis twice (didn't try that one, yet)?

Kind regards
Axel

G. Ann Campbell

unread,
Feb 6, 2018, 12:27:35 PM2/6/18
to a.von...@gmail.com, SonarQube
Hi Axel,

In fact, we're actively working on PR analysis, but it's not "done" yet, even for internal use.  We have switched over and are dogfooding an early version of this (ironically, you can currently see issues raised on the PR for the feature itself) but until it's available, you should just keep using the old GitHub plugin. Yes, I know it's deprecated, which is why we've been working almost continuously since the 6.7 release to spin up the replacement functionality in the Developer Edition. Our first target is SonarCloud so that we  i̶n̶f̶l̶i̶c̶ erm... provide this to those users for early feedback before we make it available in the commercial editions. 

Beyond that, there are additional requirements we want to meet before we make this available to you, not least of which is the ability to ensure a stable, working interaction.


HTH,
Ann 

P.S. Regarding the difference between branch analysis and PR decoration: I would say that you do want two separate analyses for now because the short-lived branch and the PR you create from it are two separate things. (Hope this makes sense.)



---
G. Ann Campbell | SonarSource
Product Manager
@GAnnCampbell

To unsubscribe from this group and all its topics, send an email to sonarqube+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sonarqube/e086a743-2864-4d72-bcd5-b2559570998f%40googlegroups.com.
Reply all
Reply to author
Forward
0 new messages