Use a sparse checkout of the macOS SDKs - #1205
Merged
Merged
Conversation
Use a sparse checkout of only the files needed during validations to speep up the checkout of the macOS SDKs repository.
Contributor
Author
|
Another method to speed up this step is to perform the checkout (sparse or full) once and cache the result for use in each job. Will look into this tomorrow. |
Contributor
Author
|
A median time for the SDK checkout of 2m10s from the merge of #1202 to 11s for the first job here. |
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
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.
Use a sparse checkout of only the files needed during validations to speed up the checkout of the macOS SDKs repository.
A full check out typically takes between 2-3 minutes although occasionally the checkout can take much longer.