Backport #64657: Use shallow clones for CI jobs

[Copilot]

Backport #64657: Use shallow clones for CI jobs

Optimize git checkout across CI jobs using shallow clones (fetchDepth: 1) and disable tag fetching.

Description

Backport of #64657 to release/9.0 (manual backport due to merge conflict with auto-backport PR #64676).

Changes:

• .azure/pipelines/jobs/default-build.yml: Add fetchDepth: 1 and fetchTags: false parameters; update both checkout steps (public/internal builds)
• .azure/pipelines/ci.yml: Add fetchDepth: 0 to Code_check job (needs full history for git log comparison in CodeCheck.ps1)
• .azure/pipelines/ci-public.yml: Add fetchDepth: 0 to Code_check job

Note: ci-unofficial.yml does not exist on release/9.0 branch.

Customer Impact

Improved CI efficiency—reduces checkout time across ~17 parallel jobs by avoiding full history/tags fetch. No customer-facing impact.

Regression?

• Yes
• No

Risk

• High
• Medium
• Low

CI-only change. No runtime code affected.

Verification

• Manual (required)
• Automated

YAML syntax validated. Changes match original PR #64657 pattern.

Packaging changes reviewed?

• Yes
• No
• N/A

---

When servicing release/2.1

• Make necessary changes in eng/PatchConfig.props

Original prompt

Backport of #64657 to release/9.0 (manual backport due to merge conflict with auto-backport PR #64676)

Summary

Use shallow clones for CI jobs to improve build performance by reducing the amount of git history that needs to be fetched.

Changes Required

Apply the following changes to the release/9.0 branch, adapting to the file structure on this branch:

1. .azure/pipelines/jobs/default-build.yml

Add new parameters for checkout optimization:

# Checkout optimization parameters
fetchDepth: 1
fetchTags: false

And update the existing checkout: self steps (there are two in the file - one for public builds around line 169, and one for internal builds around line 396) to include the fetchDepth and fetchTags parameters:

- checkout: self
  clean: true
  fetchDepth: ${{ parameters.fetchDepth }}
  fetchTags: ${{ parameters.fetchTags }}

2. .azure/pipelines/ci.yml

For the Code_check job, add fetchDepth: 0 to ensure full history is available for git log comparison in CodeCheck.ps1:

# Need full history for git log comparison in CodeCheck.ps1
fetchDepth: 0

3. .azure/pipelines/ci-public.yml

For the Code_check job, add fetchDepth: 0:

# Need full history for git log comparison in CodeCheck.ps1
fetchDepth: 0

4. .azure/pipelines/ci-unofficial.yml

For the Code_check job, add fetchDepth: 0:

# Need full history for git log comparison in CodeCheck.ps1
fetchDepth: 0

Reference

• Original PR: Use shallow clones for CI jobs #64657
• Failed auto-backport to release/10.0: [release/10.0] Use shallow clones for CI jobs #64676

/cc @adityamandaleeka

This pull request was created as a result of the following prompt from Copilot chat.

Backport of #64657 to release/9.0 (manual backport due to merge conflict with auto-backport PR #64676)

Summary

Use shallow clones for CI jobs to improve build performance by reducing the amount of git history that needs to be fetched.

Changes Required

Apply the following changes to the release/9.0 branch, adapting to the file structure on this branch:

1. .azure/pipelines/jobs/default-build.yml

Add new parameters for checkout optimization:

# Checkout optimization parameters
fetchDepth: 1
fetchTags: false

And update the existing checkout: self steps (there are two in the file - one for public builds around line 169, and one for internal builds around line 396) to include the fetchDepth and fetchTags parameters:

- checkout: self
  clean: true
  fetchDepth: ${{ parameters.fetchDepth }}
  fetchTags: ${{ parameters.fetchTags }}

2. .azure/pipelines/ci.yml

For the Code_check job, add fetchDepth: 0 to ensure full history is available for git log comparison in CodeCheck.ps1:

# Need full history for git log comparison in CodeCheck.ps1
fetchDepth: 0

3. .azure/pipelines/ci-public.yml

For the Code_check job, add fetchDepth: 0:

# Need full history for git log comparison in CodeCheck.ps1
fetchDepth: 0

4. .azure/pipelines/ci-unofficial.yml

For the Code_check job, add fetchDepth: 0:

# Need full history for git log comparison in CodeCheck.ps1
fetchDepth: 0

Reference

• Original PR: Use shallow clones for CI jobs #64657
• Failed auto-backport to release/10.0: [release/10.0] Use shallow clones for CI jobs #64676

/cc @adityamandaleeka

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[wtgodbe]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[Copilot]

Pull request overview

This PR backports optimization changes from #64657 to the release/9.0 branch to improve CI efficiency by using shallow git clones. The changes reduce checkout time across parallel build jobs by avoiding full history and tag fetching where not needed.

Key changes:

• Added fetchDepth and fetchTags parameters to the default-build template with defaults of 1 and false respectively
• Set fetchDepth: 0 for Code_check jobs that require full git history for branch comparison operations

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

File	Description
.azure/pipelines/jobs/default-build.yml	Added fetchDepth and fetchTags parameters with optimization defaults; updated both public and internal checkout steps to use these parameters
.azure/pipelines/ci.yml	Override fetchDepth to 0 for Code_check job which uses git diff against origin branch
.azure/pipelines/ci-public.yml	Override fetchDepth to 0 for Code_check job which uses git diff against origin branch

[adityamandaleeka]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[wtgodbe]

Will still fail until #64980 is in

[wtgodbe]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).