It is a Maven job. I built the Twilio ( https://github.com/twilio/twilio-java) library using all different ways. Results is 25 seconds local (both git & ssh) and 5 min 30 seconds on slave (both git & ssh)
The only odd thing that I have noticed so far is that the slave is using twice as much memory as the master when both are idle. Master is 720 GB, slave is 1.5 GB. Something seems off there. During the build the master goes to 1.91 GB and the slave to 2.74. Something seems wrong with that. Is 1.5GB on idle usage seem normal? If I disconnect the slave the memory goes to 90MB. Both the master and slave are Debian 6.0 (squeeze) installs running in virtual machines. The other thing of note is that they are in physically different locations running across a VPN. Ping time is 400ms. /Collin On Wed, May 9, 2012 at 9:02 PM, Mark Waite <markwa...@yahoo.com> wrote: > You might consider configuring various small test jobs, each using some > subset of the capabilities you need in your build. For example, use the > Git plugin, but clone a small repository from github.com with the git > protocol rather than cloning your own repository. If that is fast, then > clone a small repository from github.com with ssh. If your job is a > maven job, then try a sample maven project from outside your organization. > > Invoke a trivial Hello World job with your preferred build technique to > see if the build environment is the problem. > > Etc. > > Mark Waite > > ------------------------------ > *From:* Collin Peters <collin.pet...@gmail.com> > *To:* jenkinsci-users@googlegroups.com > *Sent:* Wednesday, May 9, 2012 3:35 PM > *Subject:* Re: Setting up slave and running a Maven build with Git takes > an unbearably long time > > My build that takes around 8 minutes locally took 3 hours and 56 minutes > on the slave!! Does anyone have *any* useful advice that would help me > diagnose this? > > My initial thought that it was an SSH issue involving reverse lookups. > However, my operations guys say that reverse lookup is working fine. That > being said, it seems that it isn't just SSH actions that are taking a long > time, as there are massive delays throughout the entire build. > > /Collin > > >
