Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: use sparse registry in deployers #773

Merged

Conversation

oddgrd
Copy link
Contributor

@oddgrd oddgrd commented Mar 30, 2023

Description of change

This switches deployers to use sparse registries, this way each deployer does not need to download the entire index before compiling a project. We might also see some performance gains in CI by switching to sparse registries, I'll try that out as well (hence the draft).

How Has This Been Tested (if applicable)?

I have deployed this to unstable and deploying a service on a fresh deployer takes about 2/3 the time. I am not seeing the new sparse registry progress bar, but we didn't see the progress bar for fetching the entire index either so maybe compiling with the cargo crate doesn't support that. 🤷

@oddgrd oddgrd force-pushed the feature/eng-500-use-sparse-registries-in-panamax branch from e74db7d to 87e50a5 Compare March 31, 2023 10:52
@oddgrd oddgrd force-pushed the feature/eng-500-use-sparse-registries-in-panamax branch from 87e50a5 to ea54194 Compare March 31, 2023 10:54
@oddgrd oddgrd marked this pull request as ready for review March 31, 2023 12:40
@oddgrd oddgrd merged commit b37c9ef into shuttle-hq:main Mar 31, 2023
@oddgrd oddgrd deleted the feature/eng-500-use-sparse-registries-in-panamax branch March 31, 2023 15:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant