We’re using CI Joe for continuous integration for one of our projects.
At first, we were so pleased with the simplicity of CI Joe, we were considering make it our go-to CI implementation instead of Jenkins of Cruise Control.
CI Joe’s main strength is its simplicity. A developer can, literally, set up CI Joe in minutes and the documentation is rather thorough.
However, something very screwy kept happening.
Every time we’d start CI Joe, it would work just fine, but, no matter what, the second commit to Github would always cause an error.
We tried pretty much everything before we stumbled onto this patch.
Interestingly, the official gem has not be updated to include this patch, so we’re building the gem from the master branch.
Because of that, our CI Joe process has a few differences.
bundle exec nohup cijoe -p 4567 . &
The above uses bundler to start CI Joe. Then, also in our Gemfile, we specify:
group :test do
gem 'cijoe', :git => 'git://github.com/defunkt/cijoe.git', :branch => 'master'
end
Once the changes get released to Rubygems, CI Joe will be back to being super easy to use.
In the meantime, if you’re not using RVM, you don’t need to worry about this fix and can use CI Joe as the instructions say.
CI Joe: We love and hate you
Commentary
CI Joe, RVM and Bundler
How we made it work
We’re using CI Joe for continuous integration for one of our projects.
At first, we were so pleased with the simplicity of CI Joe, we were considering make it our go-to CI implementation instead of Jenkins of Cruise Control.
CI Joe’s main strength is its simplicity. A developer can, literally, set up CI Joe in minutes and the documentation is rather thorough.
However, something very screwy kept happening.
Every time we’d start CI Joe, it would work just fine, but, no matter what, the second commit to Github would always cause an error.
We tried pretty much everything before we stumbled onto this patch.
Interestingly, the official gem has not be updated to include this patch, so we’re building the gem from the master branch.
Because of that, our CI Joe process has a few differences.
bundle exec nohup cijoe -p 4567 . &
The above uses bundler to start CI Joe. Then, also in our Gemfile, we specify:
group :test do
gem 'cijoe', :git => 'git://github.com/defunkt/cijoe.git', :branch => 'master'
end
Once the changes get released to Rubygems, CI Joe will be back to being super easy to use.
In the meantime, if you’re not using RVM, you don’t need to worry about this fix and can use CI Joe as the instructions say.