This is an exploratory question for @Dooruk and others here.
Namely, every so often, the route from NASA to GitHub goes through some crazy bad path and it takes forever to clone anything from GitHub.
The SI Team's usual response to this is "Use blobless clones". Indeed, I make a remark about that on my JEDI-GEOS attempt wiki instructions.
Indeed, search the internet and blobless clones are often the default for many now.
So, I'd like to add support for them here. I could pretty easily add the relevant option to:
|
git_clone_cmd = ['git', 'clone', '--recursive', '-b', branch, url, target] |
and I am 99% sure this wouldn't affect anything. I should invoke @asewnath as #38 also goes near the git bits here.
Perhaps instead it should be an true/false key-value in build.yaml to allow users to not do blobless?
I ask for debate.
This is an exploratory question for @Dooruk and others here.
Namely, every so often, the route from NASA to GitHub goes through some crazy bad path and it takes forever to clone anything from GitHub.
The SI Team's usual response to this is "Use blobless clones". Indeed, I make a remark about that on my JEDI-GEOS attempt wiki instructions.
Indeed, search the internet and blobless clones are often the default for many now.
So, I'd like to add support for them here. I could pretty easily add the relevant option to:
jedi_bundle/src/jedi_bundle/utils/git.py
Line 144 in ed1aeed
and I am 99% sure this wouldn't affect anything. I should invoke @asewnath as #38 also goes near the git bits here.
Perhaps instead it should be an true/false key-value in
build.yamlto allow users to not do blobless?I ask for debate.