Hi, indeed, great job! fwiw, there is unfortunately no rvm for windows. I have made good experiences with pik (installation appeared to be a bit tricky but that might be better now), it can also maintain different versions of ruby and jruby.
HTH, Tammo On Tue, Oct 9, 2012 at 5:30 PM, Antoine Toulme <[email protected]> wrote: > Great job Donald. Very impressed by how far you've taken this. > > I remember using the Apache Windows slave to set it up for testing. That > involved using the "Remote Desktop Client" to log on to it. > > No idea how RVM would behave in such an environment. In my recollection, I > installed Ruby and JRuby in two folders and ran from them. Back then, RVM > didn't exist. > > Antoine > > > On Monday, October 8, 2012 at 3:28 PM, Peter Donald wrote: > >> Hi, >> >> So you may have noticed I have spent a week or so intermittently >> fighting with the CI system. Unfortunately the Linux VMs that the CI >> runs on are old enough that they cause issues trying to get RVM to >> work. I have managed to get most of it working. >> >> For future reference this involved: >> * setting LD_LIBRARY_PATH to the packaged libraries in the RVM dir >> * adding begin/rescue around the doc tasks as the JRuby 1.6.7+ native >> ffi library links against a newer version of glibc than is on the box. >> (We in theory could recompile for the old ubuntu but it is easier just >> to not run using that library and avoid the documentation process >> under jruby) >> >> I believe there is still one intermittent failure (1 in 20 builds?) >> that I have yet to track down but I will look into it at some point >> later. >> >> So hopefully from now on if you see a build failure it actually means >> there is a build failure. :) >> >> Now I just need to figure out how to get the windows CI stuff working... >> >> -- >> Cheers, >> >> Peter Donald > -- Tammo van Lessen - http://www.taval.de
