Ticket #1990 (closed enhancement: fixed)
Source steps falling back to complete re-initialization should not be mandatory
|Reported by:||ayust||Owned by:|
Currently, if a source step fails to successfully update to a particular revision, it will always fall back to trying to re-initialize the repository. For some workflows, this is very bad, and it would be highly preferable for the build to just fail instead of nuking its repository and re-creating it.
The fallback to a full re-clone (or the equivalent in whatever VCS is being used) should be an option (it's fine if it defaults to on) that can be disabled if necessary.
- Keywords master-side-source-steps added
- Milestone changed from undecided to 0.8.+