CVS checkout on Jenkins via CVS plugin much slower than CVS checkout on command line or via post-build script

Question

I have configured a Jenkins project (test_cvs) via the CVS plugin to checkout a folder; lets call it CVSFOLDER. The build reports the checkout command (on console output) as:

cvs checkout -D "29 Nov 2013 11:40:33 -0800" -d test_cvs CVSFOLDER

It takes 20 minutes for this checkout to complete. If I run the same command manually on the same machine and folder where Jenkins is running, it takes 4 minutes. Similarly, if I run the same command in a post-build script in Jenkins, it takes 4 minutes.

Does anyone know the reason that checking out via the CVS plugin takes 5x the time?

Thanks.

Answer 1

I guess the answer is because Jenkins uses it's own built in CVS client.

There are a few related open issues for this:

https://issues.jenkins-ci.org/browse/JENKINS-18539

https://issues.jenkins-ci.org/browse/JENKINS-18330