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

Fix bundler caching in travis & Appveyor #1341

Merged
merged 1 commit into from
Nov 24, 2015

Conversation

johnhamelink
Copy link
Contributor

I noticed while working on #1336 that Grape is not caching Gems correctly:

screen shot 2015-11-24 at 00 39 31

This PR is an attempt to fix this.

@johnhamelink
Copy link
Contributor Author

Caching is now working. Future builds should happen much faster!

screen shot 2015-11-24 at 01 03 33

@johnhamelink johnhamelink changed the title [WIP] Attempt to fix bundler caching in travis Fix bundler caching in travis & Appveyor Nov 24, 2015
 - Point gems to vendor/bundle in travis.yml
 - Point Travis cache to vendor/bundle
 - Point Appveyor cache to vendor/bundle
@@ -12,8 +9,10 @@ rvm:
- ruby-head
- rbx-2

install:
- bundle install --retry=3
install: bundle install --path=vendor/bundle --retry=3 --jobs=3
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

weird. I thought travis just did this

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The reason it wasn't caching was because the bundle install command was explicitly defined, so it overrode whatever default travis defines. I fixed this by setting a dir to install into, then explicitly telling travis to cache that dir 😄

bf4 added a commit that referenced this pull request Nov 24, 2015
Fix bundler caching in travis & Appveyor
@bf4 bf4 merged commit 5d0cc59 into rails-api:master Nov 24, 2015
@johnhamelink johnhamelink deleted the fix-travis branch November 24, 2015 17:26
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.

2 participants