helpers: Use shallow clones for android repo#368
Open
doanac wants to merge 1 commit into
Open
Conversation
We don't need full repo histories when syncing. This will make CI a little faster and less error prone. Signed-off-by: Andy Doan <andy@foundries.io>
doanac
force-pushed
the
shallow-clones
branch
from
b228669 to
e1d1ee5
Compare
Member
|
Another option could be to save to the persistent space of factory where we also have the download and sstate cache |
Member
Author
True. But the less we require of persistent storage - the better. |
Contributor
|
What is the status of this PR? |
Member
Author
|
I think we should just merge. I think @caiotpereira - was wanting to somehow migrate customers to it. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
We don't need full repo histories when syncing. This will make CI a little faster and less error prone.