Hi Fiona, The place to increase memory is Job Configuration of your job > Build > Invoke Ant > Advanced > Java Options
What I can suggest to see if the issue comes from your CI machine or the SVN server: connect to the CI machine via ssh, run the checkout in the terminal session via the native svn client using 'svn co etc.' command and see if time differs much from what you get when Jenkins itself does the checkout via the SvnKit java library. What I can say is that checkout is long is you have lots of code: I regurlarly work on a project with 10+ millions lines of code. It takes 4 minutes to check this project out (jenkins and svn hosted on same very powerful machine from I/O standpoint: all disks are SSDs) regards didier On Feb 16, 7:02 am, fiona <bingxue0...@hotmail.com> wrote: > hi, > I open my job config, there no place to increase the -Xmx -Xms , I > increase it in my enviornment variable JAVA_OPTS,the Xmx is 1024m, Xms > is 128m, it seems like no effect. > BTW,my source code is too much. > > On 2月16日, 下午1时20分, Didier Durand <durand.did...@gmail.com> wrote: > > > > > > > > > Hi, > > > Maybe not enough memory for the JVM running the job to handle the svn > > protocol efficiently.... > > > Try to increase the -Xmx -Xms on the Java Options of your job config. > > > I would be interested to read about your results with this proposal or > > any other. > > > regards > > > didier > > > On Feb 16, 6:15 am, fiona <bingxue0...@hotmail.com> wrote: > > > > if my source code is managed by svn, when a new build start, it will > > > update first,but I find it very slow, if I execute command 'svn > > > update' alone, it is update fast. what factor maybe affect the speed?- > > > 隐藏被引用文字 - > > > - 显示引用的文字 -
