[SERVER-82555] Use shallow clone to speed up performance tests Created: 30/Oct/23 Updated: 21/Nov/23 Resolved: 21/Nov/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.2.0-rc0, 4.4.27, 7.0.5, 6.0.13, 7.1.2, 5.0.24 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Simon Eismann | Assignee: | Simon Eismann |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Backport Requested: |
v7.2
|
||||
| Participants: | |||||
| Description |
|
Evergreen supports setting the --depth parameter for git clone, which can help to speed up the cloning process significantly. If the used commit is older than the parameter set via --depth, then evergreen falls back to doing git fetch --unshallow as discussed here, which pulls the remaining commits. |
| Comments |
| Comment by Githook User [ 14/Nov/23 ] |
|
Author: {'name': 'Simon Eismann', 'email': 'simon.eismann@mongodb.com', 'username': 'SimonEismann'}Message: |
| Comment by Githook User [ 14/Nov/23 ] |
|
Author: {'name': 'Simon Eismann', 'email': 'simon.eismann@mongodb.com', 'username': 'SimonEismann'}Message: |
| Comment by Githook User [ 14/Nov/23 ] |
|
Author: {'name': 'Simon Eismann', 'email': 'simon.eismann@mongodb.com', 'username': 'SimonEismann'}Message: |
| Comment by Githook User [ 14/Nov/23 ] |
|
Author: {'name': 'Simon Eismann', 'email': 'simon.eismann@mongodb.com', 'username': 'SimonEismann'}Message: |
| Comment by Githook User [ 14/Nov/23 ] |
|
Author: {'name': 'Simon Eismann', 'email': 'simon.eismann@mongodb.com', 'username': 'SimonEismann'}Message: |
| Comment by Githook User [ 07/Nov/23 ] |
|
Author: {'name': 'Simon Eismann', 'email': 'simon.eismann@mongodb.com', 'username': 'SimonEismann'}Message: |