Repository files navigation

Adds support forR language into SonarQube. Currently, it uses output fromlintr toolwhich is processed by the plugin and uploaded into SonarQube server.

• reporting issues found by LintR (by processing its output)

• syntax highlighting
• code coverage
• code statistics (e.g. number of lines of code)

Developing a plugin on SonarQube official documentation.

InstalledJava 11 is required to run SonarQube server.

# build plugin and put it into SonarQube instance./mvnw clean package# run SonarQube server./sonar-local.sh console# wait for message: SonarQube is up# stop it by Ctrl-C

Repeat previous steps for any changes made in the plugin:

./mvnw clean package&& ./sonar-local.sh console

Check logs in different terminal session:

tail -f -n 0 ./.sonar/sonarqube-*/logs/*

Web UI is running here (admin access defaults:admin/admin)

sample-project/README.md

Follow standard procedure to add SonarQube analysis to existing project:https://docs.sonarqube.org/display/SONAR/Analyzing+Source+Code

In case the local SonarQube instance should be used, just update SonarQube server URL tohttp://localhost:9000.

For example insonar-project.properties:

sonar.host.url=http://localhost:9000

Script for the release steps:

./release.sh

Travis CI build does the release process in Github.

What it does:

• derive release version from current SNAPSHOT in POM
• create new release branch
  • commit release version into POM
  • create tag
  • push
• generate new development version by increasing last number
• checkout master
  • commit new development version
  • push