>CVS is notoriously slow when it comes to dealing with large repositories and checkouts. For example, in the wst.xsl component, we have a couple of plugins that approach 75 meg in size, and for CVS to check for changes on these plugins can take 8 to 10 minutes. That is 8 to 10 minutes wasted in a build cycle.
Eclipse now offers CVS Git mirrors. These are periodically synchronized with the main CVS repositories and provide a full copy of everything. Git is blazingly fast when detecting changes, and checking out the code.
So one option is for those wanting to speed up their builds, is to use the Git mirrors for the build. However to do this, you have to specify the port number on the build machine. According to the eclipse web masters there is some port remapping that occurs for outside users, but on the build machine you need to use something like:
Notice the 9419 port number.
Using the mirrors though also introduces some other issues from a build perspective. Depending on how your git mirrors are setup you may end up with way more than you want. In particular if your projects are setup as components within a big repository, you will get all the code from all the projects. Any change in those projects will trigger a build.
When migrating our builds, we may need to review the way we have our projects/components repositories setup. Looking at your git mirrors from CVS, do you see potential issues? I can see some with the way the current WTP Repositories are setup, and we may need to rethink our git mirrors and git repos in the future.