By far the longest part of our builds are the first step, where the build log reports it is "Checking for changes".
We have a number of CVS modules defined for each build configuration, most of which will are large library repositories, and will never change.
My questions are:
-What exactly is going on in this step? Is it running a cvs log command or what?
-Is there a way to control what is happening here?
The desired behavior is to just check out whatever we have defined in our VCS settings and run with it. There are already separate settings for each VCS configuration for when to check for changes, so I wonder what is being done different at this step in the build.