Test all virtual environments, not just the latest, and added crontab

[jwillemsen]

No description provided.

[jwillemsen]

Looks on windows-2016 jruby-9.1/jruby/jruby-head/mswin are all failing, are these known failures which I should exclude?

[jwillemsen]

jruby seems to fail because tar doesn't seem to be on the expected place on windows-2016 and mswin assumes Visual Studio 2019 which is not there on windows-2016

[MSP-Greg]

Thanks.

The problem is that a native tar.exe exists in Windows 2019, but not Windows 2016. Maybe you can experiment in your fork, as the Git or MSYS2 version may work. I can look at it later...

The mswin build is done using VS 2019, I don't think there have been any requests for a VS 2016 build. It's not a common platform, as there are some extension gems that will not compile with MSVC...

[jwillemsen]

I have updated the test.yml with the updated platforms so that all should work. My first priority is to update all our actions to use this action, maybe someone else can fix jruby on windows-2016 and enable that in the test.yml again

[eregon]

FWIW It was intentional to run a subset of platforms so the CI is reasonably fast and we don't create so many jobs. 74 jobs is still probably somewhat reasonable (but will result in a lot of queuing), so I'm OK to try with this PR and see how it goes.

Note that testing all Ruby versions on all platforms would result in hundreds of jobs and so is completely unrealistic. I don't think it's needed nor very useful either, so the proposed matrix in this PR seems OK.

[eregon]

Could you rebase this?
Most Rubies should work on windows 2016 now, except mswin: #62 (comment)

[eregon]

The 3 lines above can be removed now that #61 is fixed

[jwillemsen]

done

[eregon]

Thanks!