We are testing out a new default method to checkout code ( blobless clones ) which aims to speed up checking out source code for all users who use our built-in checkout command . If you experience issues with cloning your repo when using the built-in checkout step, please comment on this thread or ema…

[image] davidalbers: I’m seeing a similar issue where jobs have started randomly failing around a step that uses git diff. I assume it’s caused by this change since parts of commit history would be missing. @davidalbers can you send me an email at oran@circleci.com with a job link please and …

Questions - why blobless and why change the default action? I’m going to be in the minority as I use self-hosted runners, but this allows me to persist a copy of the git repo on the runner host with the result that the full git clone performed by the checkout command is an update rather than a full…

As a side note. It has been a long time since I have had to worry about the checkout step, but in the past when trying to understand what actions were being performed it was very easy as the executed shell script was included in the output of the checkout step shown in the GUI. At some point, this…

We have noticed that sonar cloud steps are failing in our builds while using blobless clones. This is a huger blocker for us as sonar is a gatekeeper for getting our PRs merged across projects. Sonar community is starting to be aware of this issue, but they do not have any permanent solutions yet. …

If you look at the step output from any workflow that is older than about 3 months you will be able to see the script run for the checkout step and so duplicate it. I do not know why, but the latest update to the checkout step has also removed this detail as I noted in a post a few weeks ago.

We are also experiencing blocking issues related to Sonar as described above by brettjohnsen-sy. [ERROR] Failed to execute goal org.sonarsource.scanner.maven:sonar-maven-plugin:3.10.0.2594:sonar (default-cli) on project xxx: java.util.concurrent.ExecutionException: java.lang.IllegalStateException: …

@sebastian-lerner In my organization, few repositories are checking-out using blobless clone, what would be the reason for that ? blobless clone should apply to all repositories in organization right ?

We also are experiencing the same problem. Our SonarScanner step has started failing consistently complaining about a “Missing blob”. Please, could you provide a solution to this problem in your documentation? Or through a parameter of the checkout command?

[Product Update] Speeding up code checkout

Build Environment

oranwild March 1, 2024, 1:53am 10

Hi @brettjohnsen-sy,

I can help out with disabling blobless checkout for you. Send the name of your organization and the project(s) you’d like us to turn this off for to oran@circleci.com. Thanks!

Topic		Replies	Views
Code checkout in CircleCI 2.0 extremly slow Build Environment	3	2529	March 22, 2018
Checkout is taking way too long Feedback & Bug Reports	2	2009	April 23, 2021
Suggestions for Speeding Up Workspace Persistence Step of Code Checkout Caching Dependencies git	2	414	June 29, 2024
CircleCI checkout seems to do shallow checkout/clone Feedback & Bug Reports	2	4194	January 5, 2019
Discussion and resolution for "ERROR: You're using an RSA key with SHA-1, which is no longer allowed" Build Environment support	16	8861	February 15, 2022

[Product Update] Speeding up code checkout

Related topics