Without this setting, travis runs 2 builds for each PR that is from a non-fork branch on one of our repos: one for the HEAD of the branch, plus one for the merge commit created by GitHub. That’s what the recent `travis-ci/push` vs `travis-ci/pr` checks we’re seeing are. Those are extra checks we don’t need that take up extra build capacity. It’s better to just build commits against the master and maintenance branches, and any PRs that target those branches.
https://travis-ci.org/rspec/rspec-support/jobs/45770207#L544 Per http://docs.travis-ci.com/user/ci-environment/ Use -Xcompat.version=2.0 per `jruby --properties` as `--2.0` wasn't being respected
I discovered that the reason travis wasn’t caching them is because it run `bundle clean` at the end just before caching the bundle, which removes the gems needed by the other repos. By having a separate bundle for each repo, each cached, we can get travis to cache them all. For #101.