| << Back to previous view |
|
[QB-1787] Server becomes unresponsive when clean workspace takes place
|
|
| Status: | Closed |
| Project: | QuickBuild |
| Component/s: | None |
| Affects Version/s: | 5.0.14 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | Joshua Thompson | Assigned To: | Robin Shen |
| Resolution: | Won't Fix | Votes: | 0 |
| Remaining Estimate: | Unknown | Time Spent: | Unknown |
| Original Estimate: | Unknown | ||
| Environment: | Windows | ||
| Description |
|
From time to time we have to clean the workspace for a configuration. e.g. This can happen if you stop a build during a subversion check-out and the working copy is broken. The configuration is unusable until it is cleaned and it often isn't possible to manually call subversion to clean up the workspace. The easiest way is to clean the workspace in Quickbuild but it completely locks the server down while the data is deleted, and no subsequent requests are responded to. For large workspaces, the server can be unresponsive for a long period of time (5+ minutes).
Why is it necessary for the server to deny all other server requests while this action is performed? |
| Comments |
| Comment by Robin Shen [ 19/Sep/13 11:49 PM ] |
|
QB should only lock your current session. Other users accessing QB should not be affected. QB locks the session for every request to prevent concurrent modifications to same session data. Normally this is not a problem, but for long running requests such as cleaning up a large workspace, it can take a long time.
You may consider to script pre-execute action of subversion checkout step to clean up workspace if previous build is canceled,or add an extra step before checkout step to call subversion clean up command under desired condition. Either way you do not need to do this manually each time a build is forcibly stopped. |
| Comment by Joshua Thompson [ 19/Sep/13 11:52 PM ] |
| Cheers for the response Robin and the suggestions. This has cleared the issue up for me so please feel free to close out this issue. |