Sugarizer: faster and tighter git clone/pull using "depth: 1" #892
Conversation
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
This was referenced Jul 13, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Downloading 700+ MB from https://github.com/llaske/sugarizer was not wise, more than half of which was stored in /opt/iiab/sugarizer-1.0/.git
This change (building on PR #888) will greatly speed up installs of MEDIUM-sized and BIG-sized IIAB 6.6/master and dramatically reduce the disk/storage footprint too.
FWIW compare this to the older approach, which had its own brittleness/maintenance/hosting costs, using files like these: