Hi there,
When Jenkins and Sonar are on the same server my build takes 25 minutes
(build + sonar analysis).
When Jenkins is on one machine and Sonar is on another it takes around 4hrs.
We use many slave build servers for Jenkins as we plan to roll out Sonar to
all our projects so it's unlikely Sonar would be run on the same machine as
the build server.
[sonar:sonar] 12:30:57.457 INFO - Execute decorators...
[sonar:sonar] 14:50:44.787 INFO - Store results in database
That's a long time of execute decorators and there are many other items
which take a significantly longer time when sonar is remote.
I've read this is due to the multiple JDBC calls directly to the database,
are there any plans to do more analysis client side then a larger dataset
push at the end to reduce the large number of individual calls.
Any comments? Is this on anyones radar?
Thanks
Chris
When Jenkins and Sonar are on the same server my build takes 25 minutes
(build + sonar analysis).
When Jenkins is on one machine and Sonar is on another it takes around 4hrs.
We use many slave build servers for Jenkins as we plan to roll out Sonar to
all our projects so it's unlikely Sonar would be run on the same machine as
the build server.
[sonar:sonar] 12:30:57.457 INFO - Execute decorators...
[sonar:sonar] 14:50:44.787 INFO - Store results in database
That's a long time of execute decorators and there are many other items
which take a significantly longer time when sonar is remote.
I've read this is due to the multiple JDBC calls directly to the database,
are there any plans to do more analysis client side then a larger dataset
push at the end to reduce the large number of individual calls.
Any comments? Is this on anyones radar?
Thanks
Chris