| Key: |
QB-169
|
| Type: |
Improvement
|
| Status: |
Resolved
|
| Resolution: |
Fixed
|
| Priority: |
Major
|
| Assignee: |
Robin Shen
|
| Reporter: |
Robin Shen
|
| Votes: |
3
|
| Watchers: |
1
|
|
If you were logged in you would be able to see more operations.
|
|
|
QuickBuild
Created: 21/Nov/06 06:27 PM
Updated: 28/Jun/08 05:42 PM
|
|
| Component/s: |
None
|
| Affects Version/s: |
None
|
| Fix Version/s: |
None
|
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
|
From Bryan,
That said, I still think it would be nice if there was either a way to
specify a build target for the "clean" option or have a setting to make
the system default for this option to be "no"; a "force sync to head"
for our Perforce depot using a typical clientspec is ~ 20 GB, and with
that much data, it's simply not an option to delete the entire source
tree as part of a regular build. It also makes any accidental "clean"
builds (using QuickBuild's clean option) pretty costly in terms of time...
|
|
Description
|
From Bryan,
That said, I still think it would be nice if there was either a way to
specify a build target for the "clean" option or have a setting to make
the system default for this option to be "no"; a "force sync to head"
for our Perforce depot using a typical clientspec is ~ 20 GB, and with
that much data, it's simply not an option to delete the entire source
tree as part of a regular build. It also makes any accidental "clean"
builds (using QuickBuild's clean option) pretty costly in terms of time... |
Show » |
| No work has yet been logged on this issue.
|
|
Be able to customize the clean build action