[
http://jira.codehaus.org/browse/CONTINUUM-1485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_108106
]
Emmanuel Venisse commented on CONTINUUM-1485:
---------------------------------------------
do you have lot of files changed between each build?
After a "cvs update", continuum run a "cvs log" to get authors, modification
dates and commit messages.
> CVS checkout is considerably slower
> -----------------------------------
>
> Key: CONTINUUM-1485
> URL: http://jira.codehaus.org/browse/CONTINUUM-1485
> Project: Continuum
> Issue Type: Bug
> Components: SCM
> Affects Versions: 1.1-beta-2
> Environment: Running on Windows XP inside Tomcat 5.5.17,
> communicating with CVSNT server, using CVSNT client.
> Reporter: Adrian Sox
>
> The project tree we are building is fairly large (5,000 files, 220 MB).
> It normally takes 5-6 minutes to perform a cvs update on this tree when
> executing from the command line or Eclipse.
> With Continuum 1.0.3, it took 5-6 minutes to update the project from CVS,
> before the actual "build" began.
> With 1.1-beta-2, it takes much longer - 15-20 minutes - to perform the same
> update. Build Fresh is not checked.
> The two versions of Continuum are set up identically in all other regards,
> except that 1.0.3 is run standalone, not from Tomcat. Both run on the same
> box, as the same user, use the same CVS executable, hit the same CVS server,
> use the same Java version, the same Maven 2 version, the same disk drive, ...
> and of course, with only one version of Continuum running at any given time.
> Aside from this issue, we very much like the changes in 1.1.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
