Openage: VMs for testing on Windows

Created on 6 Nov 2017  路  10Comments  路  Source: SFTtech/openage

Hi, I think you could use https://developer.microsoft.com/en-us/microsoft-edge/tools/vms/ for this.

Free and usable for 90 Days, then reset, repeat.

kevin to-discuss windows

All 10 comments

Hi,

The license for this "IE/Edge Windows VM" is granted by microsoft for "testing purposes only", non-commercial use, 90-days, one computer hardware and one person (no support, no warranty and no activation).

Nice

Great idea! We should probably use a qemu memory snapshot to speed up the boot process. And we'd need to install ssh and python there, with the linux subsystem this shouldn't be hard (i've never used it so far).

If somebody would like to try, this VM must provide a listening ssh service and working python3. Then of course all the necessary steps for the windows build process must either be done every build (bad) or are somehow done once with some script (much better).

Of all the folks with SSH access to our CI infrastructure, I arguably have the highest tolerance to managing Windows machines. Looks like a task for me.
Fun fact: Those modern.ie VMs come with openssh-server preconfigured and running.

  • [x] change storage to virtio
  • [x] change passwords, host keys, etc.
  • [x] disable wuauserv
  • [x] install git
  • [x] install cmake
  • [x] install VS2017
  • [x] install vcpkg
  • [x] build deps in vcpkg
  • [x] install python
  • [x] install python modules
  • [x] install opus-tools
  • [ ] do a test build
  • [ ] commit qcow2 snapshot
  • [ ] patch kevin (and chantal) to work with Windows
  • [ ] add windows vm to falk.conf
  • [ ] configure windows-specific kevinfile in kevin.conf
  • [ ] write kevinfile for openage windows builds
  • [ ] think of more stuff i forgot...

@zuntrax you can probably mark half of your list done if you use the MSVC VM instead: https://developer.microsoft.com/en-us/windows/downloads/virtual-machines

@janisozaur I had a look at that one, too, but I didn't like the fixed expiration date. Also, we are somewhat limited on storage space on the CI server, and the MSVC VM comes with a lot of unnecessary stuff preinstalled. Also I'm mostly done with the generic stuff. Right now, I'm waiting for the qt5 archive to be extracted.

Still stuck on qt5. Installation reproducibly fails with both x86-windows and x64-windows in clean vcpkg clones during packaging of the debug build. Also the new VCPKG_BUILD_TYPE variable is not yet honored by the custom cmake functions used for building qt5, trying to fix that right now. This would give me a quick workaround, since the release build works fine.

This will be handled in another repo. First PR will come soon:
https://github.com/SFTtech/kevin-win-setup

Hey there @zuntrax, any news on this one?

Seems like a job for docker/vagrant, here is a template that uses the latest dev image from ms: https://github.com/gusztavvargadr/packer/#development

Getting to it! <3

Was this page helpful?
0 / 5 - 0 ratings

Related issues

dbrgn picture dbrgn  路  7Comments

heinezen picture heinezen  路  6Comments

samuelgrigolato picture samuelgrigolato  路  4Comments

jimbob88 picture jimbob88  路  13Comments

TheJJ picture TheJJ  路  6Comments