CVS checking on Jenkins through the CVS plugin is much slower than checking CVS on the command line or through a post-build script

Question

I constructed the Jenkins project (test_cvs) through the CVS plugin to check the folder; lets call him CVSFOLDER. The line tells the checkout command (at the console output) as:

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

It takes 20 minutes to complete this check. If I run the same command manually on the same machine and the folder where Jenkins works, 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 why checking through the CVS plugin takes 5 times?

Thanks.

Answer 1

I guess the answer is because Jenkins uses its own built-in CVS client.

There are several related open issues for this:

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

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