We are using Accurev for our repositories. QuickBuild has a plugin for doing a Repository -> Checkout which we use in many of our QuickBuild workflows. Most of the time, the plugin acts as expected.
Recently, one of our Accurev streams because quite large (number of files), and now the Repository -> Checkout command never completes when attempting to checkout against this stream. In addition, whatever is being done behind the scenes between QuickBuild and Accurev is causing the workspace to become unusable. Something is getting hung up during the activity of the plugin that results in all communication between the workspace and the Accurev server to be hung, meaning issuing an "accurev info" CLI command on the workspace also hangs.
We know this works on smaller workspaces and has for years. Using the Accurev CLI, I can issue an 'accurev mkws' command pointing at the large stream and then an 'accurev update' in the workspace and there is no 'hang'. But running the "Repsository -> Checkout" does something outside of these 2 functions that is getting wedged on this exceptionally large basis stream.
Description
We are using Accurev for our repositories. QuickBuild has a plugin for doing a Repository -> Checkout which we use in many of our QuickBuild workflows. Most of the time, the plugin acts as expected.
Recently, one of our Accurev streams because quite large (number of files), and now the Repository -> Checkout command never completes when attempting to checkout against this stream. In addition, whatever is being done behind the scenes between QuickBuild and Accurev is causing the workspace to become unusable. Something is getting hung up during the activity of the plugin that results in all communication between the workspace and the Accurev server to be hung, meaning issuing an "accurev info" CLI command on the workspace also hangs.
We know this works on smaller workspaces and has for years. Using the Accurev CLI, I can issue an 'accurev mkws' command pointing at the large stream and then an 'accurev update' in the workspace and there is no 'hang'. But running the "Repsository -> Checkout" does something outside of these 2 functions that is getting wedged on this exceptionally large basis stream.