I’ve just completed another article related to Environments called “Setup – Jenkins and RVM“. In this article I take you through the setup process to get Jenkins and Ruby Version Manager (RVM) to play nice with each other. I start with the Build Server and RVM setup and then take you through to pulling your first GitHub hosted Ruby code, doing a Bundle Install and finally running a rake for your Unit Tests. I hope this will help someone out there, seeing that I have struggled to understand why things on Jenkins don’t work or why my Jenkins install doesn’t pick up that I have RVM running with the correct Rubies. It was fun and it seems to be working. So, enjoy!!! 🙂
I’ve just completed a new article called “Using – Ruby Version Manager RVM” which will be another article that I’ll refresh, change and update on a regular basis. Ruby Version Manager (RVM) is one of the best tools to use when you do Ruby Development seeing that it allows you to run multiple versions of Ruby and Gems together and to switch between these environments in an easy and straightforward way. The idea behind RVM is to have a sand-boxed environment that does not affect your system installs and can be dumped and recreated ad-hoc without having to worry that you’ll be breaking things on your system. By way of Gem Sets it also allows you to weave different Rubies together using different Gems. In all it’s an extremely powerful tool and in my upcoming article where I’ll be going into the use of Bundler and how you can use this powerful Gem with RVM, you should start seeing some of the more powerful management tools at work.
I’ve found RVM to be a life saver and can’t really imagine writing code in Ruby without it. When you start mixing in some of the other tools like Bundler, you’ll see how the power of Ruby and these tools come to life. I hope you enjoy it and that you learn something from the article and if you have feedback on the matter or if you would like me to explore certain point in more detail, please let me know.