Due to poor performance of the Windows Server 2022 vagrant playbook check job, this PR makes a number of improvements to reduce the time taken to build, notably these are:
1) The addition of the "Use Adoptium Box" option, this has only been implemented (currently) for Windows 2022, and when selected will switch the VPC job from using the standard Vagrantfile.Win2022 file, to using the Vagrantfile.Win2022.Adopt file. This 2nd new vagrantfile uses an Adoptium specific vagrant box ( stored on the vagrant server but also imported to all the VPC hosts vagrant boxes ). This vagrant box, is a fully updated ( as of 25th June ) Windows Server 2022 install, so the windows update task in the playbook is much quicker.
2) The 2nd major change, is the selective install of MSVS versions based on the JDK version selected, ( this requires the selection of the fast mode option )
JDK8 will limit the playbook to only installing MSVS_2013
JDK11 will limit the playbook to only installing MSVS_2017
JDK17 will limit the playbook to only installing MSVS_2019
JDK21/JDK22 and JDK head will limit the playbook to only installing MSVS_2022
Fixes #3553
Due to poor performance of the Windows Server 2022 vagrant playbook check job, this PR makes a number of improvements to reduce the time taken to build, notably these are:
1) The addition of the "Use Adoptium Box" option, this has only been implemented (currently) for Windows 2022, and when selected will switch the VPC job from using the standard Vagrantfile.Win2022 file, to using the Vagrantfile.Win2022.Adopt file. This 2nd new vagrantfile uses an Adoptium specific vagrant box ( stored on the vagrant server but also imported to all the VPC hosts vagrant boxes ). This vagrant box, is a fully updated ( as of 25th June ) Windows Server 2022 install, so the windows update task in the playbook is much quicker.
2) The 2nd major change, is the selective install of MSVS versions based on the JDK version selected, ( this requires the selection of the fast mode option )
JDK8 will limit the playbook to only installing MSVS_2013 JDK11 will limit the playbook to only installing MSVS_2017 JDK17 will limit the playbook to only installing MSVS_2019 JDK21/JDK22 and JDK head will limit the playbook to only installing MSVS_2022