Bryan MacFarlane

If the goal is to do matrix testing (test my code against all these versions of ruby) then I think as long as you build and populate the tool cache...

Just starting. Need to flush out more and dive a bit more into design specifics

@thejoebourneidentity @alepauly

Updated with a build and cache option

Yes, avoiding having consumers build it every time would be great. Hosted machines are a fresh VM every job. Building ruby, making it globally available and then having the setup-ruby...

@eregon - thanks, I'll have a look today.

For questions / issues on what's on the VM images (msys2 etc.), you're best to drive issues here: https://github.com/actions/virtual-environments There's multiple issues covering the what versions of ruby are available...

Thanks. Yeah, I removed because I realized it wasn't a runtime thing. If the user / workflow is also compiling extension gems then they are bringing the need for msys2...

Thanks. In general, getting tools JIT (as well as caching) is a good direction for this action to move. I think this is a product question beyond just this action...

Just to re-cap - I think step 1 is getting builds of ruby/ruby to install JIT so folks can pick ~any build. I think we can all agree on that...