Current
My company currently uses checkstyle and findbugs scripts to evaluate their code quality. I am the one who simulates these settings in a new environment managed by SonarQube.
I came to the conclusion that, when possible, I began to ask questions about the remote configuration settings of the running SonarQube server and update the local settings accordingly.
Right now, with checkstyle and findbugs, it is something like this:
1) someone changes the config xml file and uploads it to the server
2) the same person informs via email, that he changed the file and all
others need to download it
3) The others download the changed file.
Person A ---change---> settings.xml
________|____________
| | |
Person B <-------- Person C ------->Person D
The obvious problem: what if someone didn't boot? => Merge annotations explode ...
What I want
, SonarLint ( SonarQube, eclipse), , .
:
(, ), , SonarLint , . -
(, , ) checkstyle SonarQube SonarCheck. .
. yes! --> download latest version and run
. /
SonarLint ----do I have a connection?
. \
. no! --> run latest local config
, , SonarQube Jenkins
SonarQube SonarLint. , SonarLint...
? , , ?
!