Details
-
Suggestion
-
Resolution: Obsolete
-
None
Description
1) Plan A is created, initial collectChangeset
2) should do shallowClone to the R1 revision. (it should contain let's say: R0-R1 revisions, R0 is shallow)
3) repository grow up to R2-R3-R4-R5, let's assume Plan A is not collecting those changes yet
4) Plan B is created, initial collectChangeset
5) cache repository should fetch changesets since Plan A initial changesCollection, i.e it should contain R0-R1-R2-R3-R4-R5
6a) Plan A is checking the changes... it should trigger the build listing R2-R3-R4-R5 changelist.
6b) but I'm worried it might fail because local repo might have missing R2-R3 due to R4 being shallow
Attachments
Issue Links
- is detailed by
-
BAM-7437 Git repo should use shallow clones instead of full clones.
- Closed