| << Back to previous view |
|
[QB-2098] Clean up Workspaces Preserve Days seems to not take updates to workspace into account
|
|
| Status: | Resolved |
| Project: | QuickBuild |
| Component/s: | None |
| Affects Version/s: | 5.1.29 |
| Fix Version/s: | 5.1.31 |
| Type: | Bug | Priority: | Critical |
| Reporter: | Maikel vd Hurk | Assigned To: | Unassigned |
| Resolution: | Fixed | Votes: | 0 |
| Remaining Estimate: | Unknown | Time Spent: | Unknown |
| Original Estimate: | Unknown | ||
| Description |
|
Clean up Workspaces Preserve Days seems to not take updates to workspace into accountFor example:
Node A is being used on 17-06-2014 for first time with a checkout of repository, in the next 3 days this machine is being used incrementally so only checking out new changelist. If the setting for preserve workspace is set on 3 days then on the 20-05-2014 the directory is being cleaned even though this is not valid as the workspace is still being used on 18/19 and it can cause collision on the 20 when trying to use the workspace again. |
| Comments |
| Comment by Maikel vd Hurk [ 20/Jun/14 08:15 AM ] |
|
This seems to be only applicable with the fact that you have directory structure like:
root>Test>Checkout Which will result in following workspace with setting 'Use configuration name to identify workspace directory': /opt/buildagent/workspace/root/Test/Checkout This directory will have time stamp of creation for first time, eg Jun 17 02:00, but if you then perform the SCM checkout always in a subdirectory called code (/opt/buildagent/workspace/root/Test/Checkout/code), then the top directory will never get a new date and therefore during the preserve check being removed after the grace period of 3 days. |