[DPP-Devel] Changes in Continuous Integration

[Arsenij E S. <xep...@gm...>]

Hello dear devs,

I've now switched the Saros-Gerrit job, which builds whenever a new 
patchset is pushed to Gerrit, for Saros-Gerrit-Conditional.

What is different now?

Saros-Gerrit-Conditional will  only test those projects affected by the 
last commit, and will additionally provide feedback from
Sonarqube in the form of patch comments in Gerrit.

These comments come from static analysis tools such as PMD and FindBugs. 
What is commented is determined by a configuration
of rules on our Sonarqube server. Not all rules make sense for Saros, 
we've already excluded some of them, but ultimately
it's  the dev team that should decide what makes sense for the project 
and what not.

The goal is to have a configuration which is fit for Saros and the way 
we do things. For this, your active feedback is priceless.

Cheers,
Arsenij

PS Disclaimer

Also some builds might not build even though they should. If such 
cognitive dissonance occurs to you,
there's no need to hesitate to contact me or (if I am desperately 
unreachable) Franz.

The quickest way to contact me would be via Skype: arsenij.solovjev

PPS Gory Details:

Saros-Gerrit-Conditional will only compile all projects. This is 
relatively fast (2-5 minutes). After all projects have been built, a script
checks which projects have been affected by the last commit and triggers 
a QA-Job for each such project. Finally, it posts
a verified +1 or -1 to Gerrit, just as is it was before.
Each QA-Job gets the workspace from Saros-Gerrit-Conditional and 
executes tests and a Sonarqube analysis on them.
The result of the analysis will detect some issues
If all tests pass, the QA-Job will give +1. The results of the Sonar 
analysis don't matter.