Sonar runner debian package

[Guillaume Lederrey]

Hello!

I'm playing with the idea of introducing SonarQube at my new workplace. One of the things that we are going to need is a .deb package for sonar-runner [1]. As far as I can see this is not provided by SonarSource. After a quick look into sonar-scanner-cli sources [2], it seems reasonably easy to build a .deb at the same time as the .zip distribution, with something like jdeb maven plugin [3]. Would you be interested in a pull request to add this?

Thanks for the help!

[1] http://docs.sonarqube.org/display/SCAN/Analyzing+with+SonarQube+Scanner

[2] https://github.com/SonarSource/sonar-scanner-cli

[3] https://github.com/tcurdt/jdeb/blob/master/docs/maven.md

[Julien HENRY]

Hi Guillaume,

We have started an internal discussion on this topic. We are concerned about maintainability cost of such a feature (I know only very little about native Linux packaging but I fear it may be complex to properly support all distributions). We'll come back to you in a few days.

++

Julien

[Fabrice Bellingard]

Hi Guillaume,

just out of curiosity: what's your use case that needs a .deb package for the SQ Scanner? If you're setting up a continuous inspection process, then I guess you'll be using a CI tool. If it's Jenkins for instance, the SQ Scanner for Jenkins has a built-in mechanism to install SQ Scanner so no need for a special OS packaging.

Thanks!

Best regards,

Fabrice BELLINGARD | SonarSource SonarQube Platform Product Manager http://sonarsource.com

--
You received this message because you are subscribed to the Google Groups "SonarQube" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sonarqube+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sonarqube/12d68d13-5159-4c28-b1ee-31d7e9a12695%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Guillaume Lederrey]

We are using Vagrant for our developers to provide a mostly complete dev environment. Including sonar-runner in this Vagrant would ensure developers have all required dependencies at hand. Also, I'm not a big fan of Jenkins plugins, especially for something as simple as running sonar. It is much easier to keep CI configuration under source control if we have a simple entry point (script, rake task, maven, ...).

That being said, I'm not familiar at all with how our CI infrastructure is setup at Wikimedia. I might realize that this .deb package is not of that much use.

--

Guillaume Lederrey
Operations Engineer, Discovery
Wikimedia Foundation

[Fabrice Bellingard]

On Tue, Apr 5, 2016 at 5:43 PM, Guillaume Lederrey <gled...@wikimedia.org> wrote:

We are using Vagrant for our developers to provide a mostly complete dev environment. Including sonar-runner in this Vagrant would ensure developers have all required dependencies at hand.

Right. To go further, do you think this will be a common/daily task for your developers to run a SonarQube analysis on their box using the SQ Scanner? SonarLint (Eclipse/IntelliJ/Visual Studio) is probably more what they will use, no?

 

Also, I'm not a big fan of Jenkins plugins, especially for something as simple as running sonar. It is much easier to keep CI configuration under source control if we have a simple entry point (script, rake task, maven, ...).

That being said, I'm not familiar at all with how our CI infrastructure is setup at Wikimedia. I might realize that this .deb package is not of that much use.

Would be interested to have your final thoughts on that :)

[Guillaume Lederrey]

On Tue, Apr 5, 2016 at 5:59 PM, Fabrice Bellingard <fabrice.b...@sonarsource.com> wrote:

On Tue, Apr 5, 2016 at 5:43 PM, Guillaume Lederrey <gled...@wikimedia.org> wrote:

We are using Vagrant for our developers to provide a mostly complete dev environment. Including sonar-runner in this Vagrant would ensure developers have all required dependencies at hand.

Right. To go further, do you think this will be a common/daily task for your developers to run a SonarQube analysis on their box using the SQ Scanner? SonarLint (Eclipse/IntelliJ/Visual Studio) is probably more what they will use, no?

We have a lot of hardcore vim / textmate users. Not sure what the proportion of our devs use a "real IDE". So CLI is probably the first integration required.

 

 

Also, I'm not a big fan of Jenkins plugins, especially for something as simple as running sonar. It is much easier to keep CI configuration under source control if we have a simple entry point (script, rake task, maven, ...).

That being said, I'm not familiar at all with how our CI infrastructure is setup at Wikimedia. I might realize that this .deb package is not of that much use.

Would be interested to have your final thoughts on that :)

I'll let you know! Or ping me in a few weeks if you don't hear from me.

[Fabrice Bellingard]

On Tue, Apr 5, 2016 at 6:14 PM, Guillaume Lederrey <gled...@wikimedia.org> wrote:

On Tue, Apr 5, 2016 at 5:59 PM, Fabrice Bellingard <fabrice.b...@sonarsource.com> wrote:

On Tue, Apr 5, 2016 at 5:43 PM, Guillaume Lederrey <gled...@wikimedia.org> wrote:

We are using Vagrant for our developers to provide a mostly complete dev environment. Including sonar-runner in this Vagrant would ensure developers have all required dependencies at hand.

Right. To go further, do you think this will be a common/daily task for your developers to run a SonarQube analysis on their box using the SQ Scanner? SonarLint (Eclipse/IntelliJ/Visual Studio) is probably more what they will use, no?

We have a lot of hardcore vim / textmate users. Not sure what the proportion of our devs use a "real IDE". So CLI is probably the first integration required.

OK, in that case I feel that http://www.sonarlint.org/commandline/ is more what you're looking for :-)

(but it still doesn't have DEB or RPM packaging though)

[Guillaume Lederrey]

On Wed, Apr 6, 2016 at 9:17 AM, Fabrice Bellingard <fabrice.b...@sonarsource.com> wrote:

On Tue, Apr 5, 2016 at 6:14 PM, Guillaume Lederrey <gled...@wikimedia.org> wrote:

On Tue, Apr 5, 2016 at 5:59 PM, Fabrice Bellingard <fabrice.b...@sonarsource.com> wrote:

On Tue, Apr 5, 2016 at 5:43 PM, Guillaume Lederrey <gled...@wikimedia.org> wrote:

We are using Vagrant for our developers to provide a mostly complete dev environment. Including sonar-runner in this Vagrant would ensure developers have all required dependencies at hand.

Right. To go further, do you think this will be a common/daily task for your developers to run a SonarQube analysis on their box using the SQ Scanner? SonarLint (Eclipse/IntelliJ/Visual Studio) is probably more what they will use, no?

We have a lot of hardcore vim / textmate users. Not sure what the proportion of our devs use a "real IDE". So CLI is probably the first integration required.

OK, in that case I feel that http://www.sonarlint.org/commandline/ is more what you're looking for :-)

(but it still doesn't have DEB or RPM packaging though)

As far as I can see, sonarlint does not get rule sets and other configuration from SonarQube server. Which makes it not very interesting as soon as we start configuring rule sets (which we will, probably heavily). Still, I'll have a look...

[Fabrice Bellingard]

On Wed, Apr 6, 2016 at 10:47 AM, Guillaume Lederrey <gled...@wikimedia.org> wrote:

On Wed, Apr 6, 2016 at 9:17 AM, Fabrice Bellingard <fabrice.b...@sonarsource.com> wrote:

On Tue, Apr 5, 2016 at 6:14 PM, Guillaume Lederrey <gled...@wikimedia.org> wrote:

On Tue, Apr 5, 2016 at 5:59 PM, Fabrice Bellingard <fabrice.b...@sonarsource.com> wrote:

On Tue, Apr 5, 2016 at 5:43 PM, Guillaume Lederrey <gled...@wikimedia.org> wrote:

We are using Vagrant for our developers to provide a mostly complete dev environment. Including sonar-runner in this Vagrant would ensure developers have all required dependencies at hand.

Right. To go further, do you think this will be a common/daily task for your developers to run a SonarQube analysis on their box using the SQ Scanner? SonarLint (Eclipse/IntelliJ/Visual Studio) is probably more what they will use, no?

We have a lot of hardcore vim / textmate users. Not sure what the proportion of our devs use a "real IDE". So CLI is probably the first integration required.

OK, in that case I feel that http://www.sonarlint.org/commandline/ is more what you're looking for :-)

(but it still doesn't have DEB or RPM packaging though)

As far as I can see, sonarlint does not get rule sets and other configuration from SonarQube server. Which makes it not very interesting as soon as we start configuring rule sets (which we will, probably heavily). Still, I'll have a look...

Indeed, SL4CLI hasn't reached this "connected mode" yet - while it's already done in SL for VS, SL for Eclipse and very soon in SL for IntelliJ.

[Guillaume Lederrey]

On Wed, Apr 6, 2016 at 11:06 AM, Fabrice Bellingard <fabrice.b...@sonarsource.com> wrote:

On Wed, Apr 6, 2016 at 10:47 AM, Guillaume Lederrey <gled...@wikimedia.org> wrote:

On Wed, Apr 6, 2016 at 9:17 AM, Fabrice Bellingard <fabrice.b...@sonarsource.com> wrote:

On Tue, Apr 5, 2016 at 6:14 PM, Guillaume Lederrey <gled...@wikimedia.org> wrote:

On Tue, Apr 5, 2016 at 5:59 PM, Fabrice Bellingard <fabrice.b...@sonarsource.com> wrote:

On Tue, Apr 5, 2016 at 5:43 PM, Guillaume Lederrey <gled...@wikimedia.org> wrote:

We are using Vagrant for our developers to provide a mostly complete dev environment. Including sonar-runner in this Vagrant would ensure developers have all required dependencies at hand.

Right. To go further, do you think this will be a common/daily task for your developers to run a SonarQube analysis on their box using the SQ Scanner? SonarLint (Eclipse/IntelliJ/Visual Studio) is probably more what they will use, no?

We have a lot of hardcore vim / textmate users. Not sure what the proportion of our devs use a "real IDE". So CLI is probably the first integration required.

OK, in that case I feel that http://www.sonarlint.org/commandline/ is more what you're looking for :-)

(but it still doesn't have DEB or RPM packaging though)

As far as I can see, sonarlint does not get rule sets and other configuration from SonarQube server. Which makes it not very interesting as soon as we start configuring rule sets (which we will, probably heavily). Still, I'll have a look...

Indeed, SL4CLI hasn't reached this "connected mode" yet - while it's already done in SL for VS, SL for Eclipse and very soon in SL for IntelliJ.

I'm really looking forward to the IntelliJ integration!!