Question regarding pending check-ins

[tafountain]

Quick summary: we currently have manual processes to move code from one environment to another (i.e. Development to Quality Assurance to User Acceptance to Production). Our source code repository reflects that flow as well. When we actually do a full move (User Acceptance to Production for example), we check out all the code in the target environment in order to check in the copy of the code from the source environment. The problem we are experiencing is that vault appears to take literally forever to initially load the client after all the files are checked out. My question is, is there a way to disable the pending checkin list? After enabling the trace options in the vault client config file, it appears all the time is being spent performing actions related to generating the pending checkin list. Or, do you have better alternatives to accomplish the task we are trying to do?

Thanks in advance.

[lbauer]

We generally recommend against checking out an entire tree, as building a huge checkout list is a performance hit. Vault performance is better when there are fewer than 2,000 total checkouts (10 users checking out 20 files each, for example.)

You could try updating the tree in stages.

Another possibility would be to enable CVS mode in the Vault GUI Client->Concurrent Development Style, which allows you to Edit/Merge/Commit without checking anything out first.