Integrity Integrity

We were having inexplicable build failures (rake test) with Integrity running under Phusion Passenger. We could successfully run the build script from the builds/CHECKOUT/MD5 directory, but any time the script was invoked by Integrity, the builds would fail with an error related to loading fixtures.

I traced the problem to the fact that when Integrity launches the build script, it uses IO.popen(...), which launches a new process that inherits the current process' environment. This means the build script runs with the RUBYOPT, GEM_HOME, GEM_PATH and PATH of the Merb app. Calling rake in the build script would invoke integrity/bin/rake, and RUBYOPT included Integrity's bundled gems environment.rb. Both of these appeared to be causing the problem.

By resetting these ENV variables within our build script, we were able to make our build work properly again:

export PATH=/usr/local/bin:/usr/bin:/bin
unset RUBYOPT
unset GEM_HOME
unset GEM_PATH
...
rake test

I'm not sure what specifically can be done to fix this in Integrity, as I believe all methods of launching child processes inherits the ENV. It might be helpful to include a sample build script that documents this behavior.