Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Default fetch and clone depth to 1 #444

Closed
dtanner opened this issue Nov 23, 2021 · 0 comments · Fixed by go-vela/vela-git#90
Closed

Default fetch and clone depth to 1 #444

dtanner opened this issue Nov 23, 2021 · 0 comments · Fixed by go-vela/vela-git#90
Assignees
Labels
area/plugin Indicates a change to a plugin area/server Indicates a change to the server enhancement Indicates an improvement to a feature good first issue Good for newcomers

Comments

@dtanner
Copy link

dtanner commented Nov 23, 2021

Description

Default the fetch/clone depth to 1 to reduce the amount of data pulled down during the clone step

Value

There are examples of projects whose full repo size is over 700MB, whereas their depth of 1 is a third of that size. Their clone step currently takes 30 seconds, so reducing that size will have a positive impact on build performance and network usage.

Definition of Done

The default depth for clone/fetch steps is 1. Docs are updated accordingly.

Effort (Optional)

1 day

Impacted Personas (Optional)

users will benefit mostly.
one caveat is that this could increase cpu load on the github servers, so need to confirm with those admins about the change.

@dtanner dtanner added the enhancement Indicates an improvement to a feature label Nov 23, 2021
@wass3r wass3r added area/plugin Indicates a change to a plugin area/server Indicates a change to the server good first issue Good for newcomers labels Nov 23, 2021
@dtanner dtanner self-assigned this Dec 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/plugin Indicates a change to a plugin area/server Indicates a change to the server enhancement Indicates an improvement to a feature good first issue Good for newcomers
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants