[CI] Add Ruby 3.1, OS to numeric, Windows #491
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The Actions windows-2016 & 2019 images have mingw build tools installed. The new windows-2022 image only has a bash shell and pacman installed.
So, when using the windows-2022 image, ruby/setup-ruby now installs the mingw64 or ucrt64 toolsets. Since the additional size of the packages needed to build Ruby is negligible, those packages are also installed. This means that the only reason for using MSP-Greg/setup-ruby-pkgs is the Windows mswin build.
Since the code for that is rather simple (install openssl-dev, etc), I switched to ruby/setup-ruby and added a short PowerShell script to account for the mswin job.
EDIT: There are some excepts to the above, but only with Windows Rubies 2.4 and earlier. If one needs to build with OpenSSL on 2.4, MSP-Greg/setup-ruby-pkgs needs to be used, as 2.4 was built with OpenSSL 1.0.2. Windows Ruby 2.3 and earlier need MSP-Greg/setup-ruby-pkgs for all package installations, and there are very few available (they were built with MSYS, not MSYS2).