Writings on various topics (mostly technical) from Oliver Hookins and Angela Collins. We have lived in Berlin since 2009, have two kids, and have far too little time to really justify having a blog.
So I was going to post a comment on the original blog post which I linked to from here but Facebook connect was broken and I don't feel like setting up yet another account </1stworldproblems>... but there was a slight development.
I attempted to use the same methodology we had already followed with the first app, to another app so that this one was also packaged using Bundler and RPM. Needing to confirm that all was well before I committed the changes I did some testing in a CentOS virtual machine in Vagrant. To be expected, with a deployment bundle of a decent few gems the package size comes out at around 15MB. I committed the changes and the produced RPM from the Jenkins build job was 50MB. Why?
Initially, I suspected subtle differences in Bundler gem versions,
library path differences etc but these ended up being dead-ends. What
was happening, however, was that the gems were being installed into
apprepo/vendor/ruby/1.8, including the excluded groups. I am assuming
this is a necessity for the tests and other build-time checks to run,
but I certainly didn't want them to be packaged with the RPM which can
rely on just the gem cache.
As it turns out, Bundler has some "smart" code around user permissions - specifically around what commands you can run through
standard Vagrant box will have unrestricted sudo access for the
vagrant user, so it can install gems anywhere. Bundler uses this fact
to its advantage and will install them into the standard
/usr/lib64/ruby/gems/1.8/gems/ path. Hence, when it comes time to
package up the gems as an RPM, these files are not in the app build path
and the RPM stays a slim 15MB.
In our build pipeline which uses a standard user account on a fairly
normal CentOS install, the
jenkins user has no such permissions and
thus has no option but to install them into the vendor directory along
with the other Bundler artifacts. The solution was simply to exclude
this directory from being packaged, although I'm still not entirely
sure why we didn't hit this problem the first time around.
Nevertheless, bearing in mind these few gotchas, we now have a system in
place that makes it a snap to add more gems and maintain a well-packaged
and stable application from development to production.