Skip to content

Commit

Permalink
Fix 'Your Gemfile.lock is corrupt.' on Travis CI
Browse files Browse the repository at this point in the history
couple of things changed due to rubygems/bundler#4467

incl. Ruby (RVM) bump from 2.2.5 to 2.3.1 (just to be in line with local)
  • Loading branch information
vorburger committed Dec 2, 2016
1 parent 6e91a1f commit 834002b
Show file tree
Hide file tree
Showing 4 changed files with 23 additions and 161 deletions.
5 changes: 5 additions & 0 deletions .gitignore
Original file line number Diff line number Diff line change
@@ -1,3 +1,8 @@
_site/
.sass-cache/
.jekyll-metadata
.bundle/
vendor/

# https://github.com/bundler/bundler/issues/4467
Gemfile.lock
4 changes: 3 additions & 1 deletion .travis.yml
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,9 @@ sudo: false # route your build to the container-based infrastructure for a faste
language: ruby

rvm:
- 2.2.5
- 2.3.1

install: bundle install

script: ./.travis.sh

Expand Down
160 changes: 0 additions & 160 deletions Gemfile.lock

This file was deleted.

15 changes: 15 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -14,6 +14,21 @@ Your contributions are more than welcome!

## Troubleshooting

Use `rm -rf .bundle/ vendor/ ; git clean -fX` to solve this problem if it occurs locally:

```
Your Gemfile.lock is corrupt. The following gem is missing from the DEPENDENCIES section: 'mini_portile2'
```

and if it occurs on Tracis CI then add `install: bundle install` to `.travis.yml`
and git rm Gemfile.lock && echo "Gemfile.lock" >>.gitignore;
needed because its default is `bundle install --jobs=3 --retry=3 --deployment`,
the `--deployment` if a `Gemfile.lock` exists,
see https://docs.travis-ci.com/user/languages/ruby/#Travis-CI-uses-Bundler,
and that is causing some issues, see https://github.com/bundler/bundler/issues/4467.


Use `sudo dnf install ruby-devel` to solve this problem:

```
Expand Down

0 comments on commit 834002b

Please sign in to comment.