Hi Christian,

I've played a bit with .rvmrc support. I don't want to redirect all execution to rvm-shell because people use rake runner not only for Ruby projects, also for some .NET projects. So such people may want to pass rvm environment not only to CommandLine and Rake build runners, but also to some other runners type. So general solution is to fetch all environment variables using rvm-shell script and then pass it to all build steps. As far as I understand such rvm-shell emulation has the same behaviour as commands redirecting to rvm-shell script.

So Ruby env configurator build feature will provide 3 ways for specifing interpreter

1. ruby interpreter path (e.g. for Windows guys)

2. rvm sdk & gemset name (for those how don't want use .rvmrc settings, e.g. to run tests on different ruby interpreters instead of hardcoded in .rvmrc file) Here most likely I'll replace current implementation with rvm-shell environment variables way

3. .rvmrc (TC will fetch env variable using rvm-shell and will pass it to all build steps)

3rd way is DRY but not flexible, you miss some advantages of CI because better to run tests on different interpreters.

P.S: rvm-shell support will be added only in 6.5.2 or later. 6.5.1 is almost ready and it includes fix for regression in passing ruby env. build feature settings to cmdline build runner.