[SERVER-22329] Investigate where we can use git clone --depth=1 in evergreen.yml Created: 27/Jan/16 Updated: 06/Dec/22 Resolved: 23/Oct/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | 3.3.0 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Robert Guo (Inactive) | Assignee: | [DO NOT ASSIGN] Backlog - Decision Automation Group (DAG) (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | close, tig-evgconfig | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Decision Automation Group
|
||||
| Participants: | |||||
| Description |
|
We are cloning a number of repositories for different tasks in evergreen.yml. We should investigate which of these clones can be speeded up with git clone --depth=1 |
| Comments |
| Comment by Mark Benvenuto [ 27/Jan/16 ] |
|
Evergreen often has to clone back several revisions, particularly in stepback. This would also be true in patch builds. Is only depth=1 optimized or is depth=10 also good? |