| << Back to previous view |
|
[QB-179] Be able to do a 'force checkout' in a repository
|
|
| Status: | Resolved |
| Project: | QuickBuild |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major |
| Reporter: | Don Ross | Assigned To: | Robin Shen |
| Resolution: | Fixed | Votes: | 0 |
| Remaining Estimate: | Unknown | Time Spent: | Unknown |
| Original Estimate: | Unknown | ||
| Description |
|
My specific use case is this: I have a File System repository which I use to download a set of data files from a server, which I then use in my build. During the build, these data files get modified, used to generate a zip file, and then can be discarded. When I trigger the next build, however, the checked out files are not overwritten by the Checkout step, because they are the same or newer than those in the repository. I had to write a special Builder step to remove the files before calling the Checkout step. Please add a flag to the File System repository which forces a clean sync of all files in the repository which are different from (not just newer than) those already checked out. I can also see where this capabilty may be useful for other types of repositories, where checked out data may be modified or deleted. If set, the Checkout action should do whatever is necessary to make the checked out files match those in the repository. |
| Comments |
| Comment by Robin Shen [ 15/Dec/06 05:18 PM ] |
| How about do a clean build? When a clean build is executed, all files will be deleted first. |
| Comment by Don Ross [ 16/Dec/06 11:35 AM ] |
|
My perforce repository has 12gb of data, much of which doesn't change very often. It takes an hour and a half to do a full sync... so a clean build twice a day isn't really an option. A happy medium would be the ability to force sync select repositories. Then I could force the File System repository to sync clean every build while only cleaning the perforce sync once a week. I am imagining an option to the Checkout step. |
| Comment by Robin Shen [ 16/Dec/06 06:52 PM ] |
| Thanks, will take care of this. |
| Comment by Robin Shen [ 02/Mar/10 01:48 AM ] |
| The cleanup strategy is left to the user since 2.0, and this functionality can be achieved by supplying pre-execute script cleaning necessary files/directories for the build step. |