Further optimize Git clones

Open
#865 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Tech stack
git, python
Domain
devops, performance

Research direction

Read the linked GitLab article, then inspect how Taskgraph configures Gecko clones and where clone timing is measured. Identify concrete optimization candidates and define done as a documented, tested improvement over the roughly two-minute shallow-clone baseline.

Written by the indexing model from the issue text.

Description

We started using shallow clones in Gecko to get clone times down to ~2 minutes, but I think there are further optimizations we can make. Marco recently shared this article which contains a bunch of tips:
https://about.gitlab.com/blog/supercharge-your-git-workflows/

I won't have time to prioritize this, so filing an issue to track it for now.

Dominant language
Python
Stars
26
Forks
55
Avg merge
2d 6m
Merged PRs (30d)
15

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from taskcluster/taskgraph

All issues in taskcluster/taskgraph

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.