Hi, On Fri, Jan 29, 2010 at 10:27 PM, Jukka Zitting <jukka.zitt...@gmail.com> wrote: > I had a few spare moments so I set up a Sonar instance at > http://sonar.zitting.name/ (to be moved to Apache hardware later, see > INFRA-2140 [1]) and I'm planning to install the Sonar plugin in Hudson > and set up a test build job that uses this feature. The new plugin may > require a Hudson restart.
I installed the Sonar plugin and restarted Hudson yesterday morning when there were no build jobs pending. The Sonar plugin seems to work fine at least for the two projects (Jackrabbit and Tika) I used for testing. However, the PostgreSQL connection from the Hudson servers (in USA?) to my Sonar server (in Finland) is really slow, adding over five hours of extra time to updating a big project like Jackrabbit (>200kLOC). This is quite annoying even if it typically makes most sense to do Sonar updates only about once per week or month. 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. BR, Jukka Zitting
