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

During deploy, skip bundle install when Gemfile.lock has not changed #69

Open
martinemde opened this issue Oct 9, 2013 · 2 comments
Open
Labels
Milestone

Comments

@martinemde
Copy link
Contributor

Use the same utility that assets checking is using to determine code changes and only re-bundle when something has changed. Probably want to check vendored gems too.

@tmiller
Copy link

tmiller commented Nov 18, 2013

I understand that bundler has gotten more intelligent about when it downloads gems, and I checked a deploy log and my bundle command ran within a second since the Gemfile.lock did not change. Is this still something you still want to pursue?

@martinemde
Copy link
Contributor Author

I think you're right. According to the changelog in bundler we should be able to speed up installs significantly without doing anything fancy. I'll leave this ticket on hold until we can see how bundler 1.5.0 does and if it solves the slow install issues enough for most people.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants