| << Back to previous view |
|
[QB-2406] QuickBuild Repository Snapshot Toggle
|
|
| Status: | Closed |
| Project: | QuickBuild |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor |
| Reporter: | J. Mash | Assigned To: | Robin Shen |
| Resolution: | Won't Fix | Votes: | 0 |
| Remaining Estimate: | Unknown | Time Spent: | Unknown |
| Original Estimate: | Unknown | ||
| Description |
|
This is a request to add a setting or toggle to the QuickBuild repository type that allows me to dictate when the snapshot is taken. There are two settings that I would find valuable for this:
- Automatic: Allow QuickBuild to take the snapshot at the beginning of the build, as it does currently. - Manual: Do not allow QuickBuild to take the snapshot, and instead rely on the user to dictate when the snapshot should be taken by calling "repo.takeSnapshot()" at the appropriate time. This can currently be emulated by specifying a script in the "Advanced Setting' page for each configuration, but this can get cumbersome to manage in some circumstances. The addition of a toggle would make things much cleaner. |
| Comments |
| Comment by Robin Shen [ 16/Jan/16 03:20 AM ] |
| Also we can not add this feature as QB internally has to forcibly take snapshot at start of the build to make it repository revision consistent across the build (either for change calcuation, label step, or checkout step, etc.). Make this option may cause many issues for common use cases. |
| Comment by Robin Shen [ 16/Jan/16 03:22 AM ] |
|
Instead for scenarios where user want to postpone snapshot taking to later phase in the build, they can always call below code to force QB to re-take snapshot:
repositories.get("repo").setRevision(null); repositories.get("repo").takeSnapshot(); Our rule is to make QB simple for common use cases, and make it possible for special cases via scripting. |
| Comment by J. Mash [ 16/Jan/16 04:37 AM ] |
|
That's what I'm doing currently, so I will continue to do that. It is a bit cumbersome to have to cargo-cult this script around from configuration to configuration, but you are right that it's possible.
Thanks for the response, and please feel free to close this out, if you want. |