Summary

WT Evergreen compile tasks check out the WT repository before building. The checkout repeats across build variants and adds setup time to each compile task. Unit-test tasks that reuse compile artifacts do not perform another repository checkout.

Current behaviour

• The base compile tasks in wiredtiger and wiredtiger-disagg call git.get_project without a clone-depth limit, so the source checkout includes repository history.
• Compatibility and code-change tasks also inspect release tags or commit ancestry.

Proposed solution

Use a bounded history for compile-task checkouts that only need the target revision, while retaining full history for tasks that inspect tags or commit ancestry. Validate the compile tasks and history-dependent workflows before extending the change.