<https://lh5.googleusercontent.com/-FkvzJAD5vTM/Uuaf3r38bhI/AAAAAAAAABk/s_zYjkeQ9DY/s1600/svnUpdate.jpg><https://lh3.googleusercontent.com/-LBLgE6r4-WU/Uuag9E3UAuI/AAAAAAAAAB0/4lfLX0vUQZ4/s1600/svnUpdate2.jpg>
This is frustrating. I cannot explain why it takes so long... Is anybody able to explain me what is happening during process* "Updating..."* Which lasts ~5 minutes Then * "At revision no change for ...."* Which lasts another 5 minutes? Does somebody know the complete command line if any used by jenkins to update the working copy or any tip to debug this? Thank you On Thursday, January 23, 2014 2:35:16 PM UTC+1, kgiloo wrote: > > > what is probably a no-go for the integration of our linux builds with > jenkins' job per node..: > redhat 5.5 > checkout: nearly one hour on SSD (few minutes only using the svn client > command line) > > even simple 'update' is very slow and takes huge time just to be kicked, > don't know why. > > Updating > https://<https://svn.autoform.ch/svn/AutoForm/Redesign/feature_branches/gk_test/Trunk_j> > ... > (waiting 10 minutes to pass this) > ... > > Don't seem to have such a problem on windows nodes. > Any explanation? > > BTW, having the possibility to configure svn by defining local svn path > per node instead of depending on svnKit (probably deficient implementation) > would be a great option! > > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
