Hi,
I’ve just manually started a build and the configuration repository has been at the status of “Updating cache” for over 20 minutes. Can you please help me understand what that means, why it’s taking so long and how much longer I could potentially expect it to take?
The last check-in effectively deleted and re-added all files to the repository in plastic. I don’t know if that’s a clue or not?
Regards,
Sean
Hi Sean,
Apologies for the delay responding, I didn’t get a notification for this post for some reason.
The “Updating cache” status is shown when the repository is downloading files from your repository to the repository cache working folder and then adding them to the repository cache (which is a Mercurial repository).
With PlasticSCM repositories this will run “cm update” after first ensuring that the workspace folder is a clean version of the previous changeset using “cm unco”, “cm unc” and “cm fp” as necessary. The Mercurial “hg commit” command is then run to update the repository cache.
As you added a large number of files, I suspect that it is taking some time to download the changes. You can find more detail on what is happening in the debug log.