Hi, On Mon, Feb 1, 2010 at 5:38 PM, Jukka Zitting <jukka.zitt...@gmail.com> wrote: > To avoid the excessive database connection overhead we could either > install Sonar somewhere closer to the Hudson servers, or turn the > Sonar server into a Hudson slave that's dedicated to running Sonar > update jobs.
How about if we install Sonar as another webapp on the Hudson master, at http://hudson.zones.apache.org/sonar/? I've played a bit more with my installation and it looks like the load caused by the Sonar webapp and the underlying database is relatively low, all the heavy lifting happens in the analysis phase (mvn sonar:sonar, etc.). Thus having a separate server for Sonar doesn't seem necessary, at least for now. We can always relocate it to a different server if it becomes too popular. BR, Jukka Zitting
