How to bind multiple projects to SonarQube efficiently


(Robert Lichtenberger) #1

I am running a local sonarcube that successfully checks our 110 Projects for issues.
I have also setup the SonarLint for Eclipse plugin Version in Eclipse Version: 2018-09 (4.9.0)

To bind a project to the SonarQube I can now open the context-menu on any project, choose SonarLint -> Bind to SonarQube or SonarCloud and choose my server connection. The following dialog will even present me with a good SonarQube project to bind my eclipse project to.

But doing this 110 times is very tedious. I remember that in earlier versions there was a “wizard” kind of a dialog where you could hit an “auto-bind” button and all eclipse projects would be mapped to their SonarQube twins, which was very nice an efficient.
Has this feature been removed from SonarLint?

(Julien Henry) #2


You can select multiple projects to bind, or a working set, as long as all Eclipse projects should bind to the same SonarQube project (usually in multi-module projects).

But if the Eclipse projects are actually different SQ projects, then currently you have no choice than binding them one by one.

(Robert Lichtenberger) #3

Our eclipse projects should each bind to their respective SQ project. Earlier versions of SonarLint did support auto-binding them individually. This is a real showstopper for us.

(Julien Henry) #4

I see the point. I have created a ticket:

But we are currently busy to prepare SQ LTS, so I don’t think you should expect any progress before the second half of the year.