Allow for Shallow Clone command in 2.0 | Feature Requests

Allow for Shallow Clone command in 2.0

David Aghassi

As per https://github.com/circleci/circleci-docs/issues/2040#issuecomment-368139737
It would be nice for users to have a way to shallow clone. Currently, we do checkout
 to checkout. It would be nice to be able to pass a depth into that like shallowClone:10
 and then use the number 10
 as the depth for the clone. The PR linked has a modified version of the existing script that works.
CCI-I-254

February 27, 2018

Oran Wilder

[UPDATE] We have rolled back the blobless clone preview mentioned in January, and are evaluating a new path forward based on your feedback.

Sebastian Lerner

Hi folks, we are testing out something similar to a shallow clone (a blobless clone https://github.blog/2020-12-21-get-up-to-speed-with-partial-clone-and-shallow-clone/) that aims to speed up checkouts.

If you want to try this out in "beta", email me at sebastian@circleci.com

Manuel Fittko

weird, that this is still not offered, could be a simple optional param or env var for the

checkout

step, no?

Surenkumar Nihalani

Can we prioritize this please?

Anton

so pity such a simple and necessary thing is ignored by the CircleCI team. So now everyone has to use some thirdparty orbs or implement this by themselves...

For our company shallow copy speeds up the cloning from 22 seconds to 6 and this is multiplied to many different steps.

Thibaut

Anton: which orb are you using?

Anton

Thibaut: none, had to implement this by ourselves but we have a private orb

Thibaut

What it take so long time to add a simple parameter to the checkout command ?

Ricardo Oliveira

A shallow clone should even be the default I'd think. https://github.com/circleci/circleci-docs/issues/2040#issuecomment-646590921

Steve Sims

FYI, shallow cloning is the default in GitHub CI's checkout action, defaulting to a depth of 1

Hirokuni Kim

Does this help? https://circleci.com/orbs/registry/orb/ganta/git

Brett Hardin

I'd love to have this ability. We attempted to use the cacheing step for our source as Jonas T suggests, but the cache fails about 30% of time time, which means the whole build fails. Not ideal. Any idea as to if/when this will be implemented?

→