| << Back to previous view |
|
[QB-125] Renaming Configurations with Builds is unpredictable
|
|
| Status: | Resolved |
| Project: | QuickBuild |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | Matthew Inger | Assigned To: | Robin Shen |
| Resolution: | Fixed | Votes: | 0 |
| Remaining Estimate: | Unknown | Time Spent: | Unknown |
| Original Estimate: | Unknown | ||
| Description |
|
If i have a configuration with several builds in it, and I rename that configuration, it seems to take forever to complete in the browser window. At times, it does not ever rename the publish directory, and I have to manually rename it in the filesystem. And in one instance, it crashed the server, and I lost all the builds on disk that i had in that configuration. I would think a rename of a configuration would be a simple as: 1. Change the db entry 2. rename the publish directory on disk 3. rename the work directory on disk I'm not sure why it's taking so long for this operation to run (which seems to be the major issue, given the size of our build artifacts > 400 MB). At the very least, this operation should not be expected to complete in a single browser request if soemthing more complicated is going on. |
| Comments |
| Comment by Robin Shen [ 29/Aug/06 06:34 PM ] |
| QuickBuild should simply rename the directory. What operating system are you using? |