Bundle(r) Yourself… and Get Ready to Cruise!

November 17, 2009 Pivotal Labs

On a current project, we’ve just switched from GemInstaller to Bundler for managing our application’s gems.

All in all, the transition was painless… in our development environments. Of course, in order to keep things on running smoothly on the continuous integration box, we amended our rake cruise:spec task to start by running sh "gem bundle".

So, wonderful! Any changes to our gem dependency list will picked up when cruise starts and made available for that “build”; there’s no need to log in and make any manual updates. Right?

Not quite. We’re using the disable_system_gems option and, in that case, Bundler (very intentionally) modifies your GEM_PATH such that only “vendor’d” gems are available to the application. Which of course means that Bundler itself, being “a gem to bundle gems”, is unavailable when that sh "gem bundle" command is run.

Our solution: bundle Bundler, obviously! That’s right, in our Bundler Gemfile we’ve included gem "bundler". Now, after a single manual execution of gem bundle to pick up the bundled Gem Bundler gem bundle (heh), any subsequent Gemfile changes (to gems other than Bundler) get picked up at the start of the build… and we’re cruisin’

Have another solution? Please let us know in the comments.

About the Author

Biography

More Content by Pivotal Labs
Previous
Color My Mustache Update: Double Down and Split
Color My Mustache Update: Double Down and Split

Please see my previous post regarding Movember for context. Pivotal Labs CEO Rob Mee has announced that he...

Next
Want a new challenge? Come work for Pivotal clients!
Want a new challenge? Come work for Pivotal clients!

At Pivotal Labs, one of the services we provide is bootstrapping startups, including helping them interview...

How do you measure digital transformation?

Take the Benchmark