| << Back to previous view |
|
[QB-1892] Deleting of all workspaces in case you delete configurations should be optional
|
|
| Status: | Resolved |
| Project: | QuickBuild |
| Component/s: | None |
| Affects Version/s: | 5.1.3 |
| Fix Version/s: | 5.1.5 |
| Type: | Bug | Priority: | Critical |
| Reporter: | Maikel vd Hurk | Assigned To: | Unassigned |
| Resolution: | Fixed | Votes: | 1 |
| Remaining Estimate: | Unknown | Time Spent: | Unknown |
| Original Estimate: | Unknown | ||
| Environment: | 5.1.3 | ||
| Description |
|
Deleting of all workspaces in case you delete configurations should be optional. In large environment like we have there are some global workspaces on our build servers which are now being removed once a configuration is being deleted. This force deleting of all workspace should be an option which could be marked when you are going to delete configuration. Also I think that the deleting of workspaces should only be done in case the Workspace Directory Setting is set to 'Use configuration name to identify workspace directory' and not in case you make use of 'Use specified workspace directory'
For example: On Windows node we have generic path to avoid path length problem with VS build, so therefore we make use of 'Use specified workspace directory" which is similar for each SCM repository where we build the Windows target. |
| Comments |
| Comment by Lukasz Guminski [ 20/Dec/13 11:28 AM ] |
| I believe that this feature creates a hole in QB security model. A malicious user without permissions to a given configuration is able to remove all its workspaces, by creating another config pointing to the same workspace location, and removing it. |
| Comment by Robin Shen [ 21/Dec/13 02:12 AM ] |
| We will add the extra check to only remove workspace when workspace setting is defined as "use configuration name to identify workspace directory" in next patch release. |