Ruby on Rails. Bundler. Cucumber. Rake Aborted! Command Failed with Status (1)

cucumber, rake aborted, command failed with status 1

Try adding nokogiri in your Gemfile and run bundle install

If that does not work, update your question and add your env.rb file and your Gemfile.lock

Cucumber : Command failed with status (1) with rake features

While I am not sure this relates exactly to your issue, but RSpec 2.x is Rails 3.x only. You will want RSpec 1.3.x for use with rails 2.3.x.

Command failed with status () when precompiling assets

I am going to answer this myself because I could solve it more or less. If someone has additions, don't hesitate to write an own answer or comment this answer/question.

What I've found out so far:

If you play around with assets:precompile by e.g just compiling the primary assets (assets:precompile:primary) or explicitly calling assets:precompile:all you might end up with a hint about the source of your problem. In my case, I ran into Errno::EACCES on both public/ and tmp/. Somehow that was not displayed, so make sure your user has full rights to create/delete files and folders there.

In my case, it worked sometimes because I've shut down the rails app and precompiled while it was down. Since precompiling allocates a lot of memory, I did some trial and error and eventually got the known Killed message when rake tries to execute asstes:precompile:primary. The task simply was killed because of using too much memory.

Another problem was that sprockets could not find bootstrap to put it into the assets pipeline on precompilation. Moving gem 'bootstrap' outside of group :assets solved this. This was also something I got hinted to when I played around with the commands.

The best way to solve – or better: work around – this problem is to simply compile your assets locally. Just throw a rake assets:precompile RAILS_ENV=development into your terminal and then deploy public/assets. Remember to delete that folder in your development environment after deploying it or you will end up debugging on why your changes on app/assets/* are not taking effect in development. At least that works for me(tm).

Alternatively, growing your swap partition may also work. However, compilation on a VPS where you need to use swap may take its while, so I'd stick to the local way.

rack and cucumber; not sure how to resolve

You may try creating a temporary gemset and install bundle over there and try it out, following are the step to follow,

rvm gemset create temp_gemset
rvm gemset use temp_gemset
bundle install

Here temp_gemset is the name given to gemset

Cucumber features failing undefined method `Factory' with bundler, rails 2.3.5

This is an issue with bundler crapping out because I declared factory_girl in more than one group. http://github.com/carlhuda/bundler/issues/issue/135 Until this fix is incorporated into a release, either pull down the bundler gem from github or don't put a gem in your Gemfile into more than one group.

cucumber: command not found error on command line; rake cucumber works fine though

The error message you're getting from bash and the fact that which cucumber doesn't give any output indicates that the cucumber executable is not on your path. Check the RubyGems path by running gem env and update your operating system path accordingly.