You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Eagerly awaiting the release of the sparse checkout feature requested under #4325 I was doing some testing of the task and have noticed the sparse-checkout is performed after the fetch, this results in the full fetch being performed and the sparse-checkout effectively being a delete on the file system. The problem with this approach on an agent is it does nothing to speed up the checkout of large repos or cut down the disk required.
Unless I'm mistaken the fix won't be as simple as moving the sparse-checkout activities to before the fetch as the fetch is used for the initial setup of the repo, as a result I think there needs to be a rework of the initial setup to possibly one of the following patterns
Init
Add remote
Configure sparse
Fetch
or
Clone with --no-checkout
Configure sparse
Fetch
Of course not all checkouts are with sparse options so any pattern needs to fit in with the existing capabilities
Versions
Azure DevOps v4.248.0
Environment type (Please select at least one enviroment where you face this issue)
What happened?
Eagerly awaiting the release of the sparse checkout feature requested under #4325 I was doing some testing of the task and have noticed the
sparse-checkoutis performed after thefetch, this results in the full fetch being performed and the sparse-checkout effectively being a delete on the file system. The problem with this approach on an agent is it does nothing to speed up the checkout of large repos or cut down the disk required.Unless I'm mistaken the fix won't be as simple as moving the sparse-checkout activities to before the fetch as the fetch is used for the initial setup of the repo, as a result I think there needs to be a rework of the initial setup to possibly one of the following patterns
or
Of course not all checkouts are with sparse options so any pattern needs to fit in with the existing capabilities
Versions
Azure DevOps v4.248.0
Environment type (Please select at least one enviroment where you face this issue)
Azure DevOps Server type
dev.azure.com (formerly visualstudio.com)
Azure DevOps Server Version (if applicable)
No response
Operation system
No response
Version controll system
No response
Relevant log output
The text was updated successfully, but these errors were encountered: