jimklimov
commented
3 years ago Bookmarking a couple more findings: apparently Microsoft itself now issues (temporarily valid) VMs that can be used for building and/or testing stuff. This may be useful even when NUT CI life continues beyond Travis.
The list found so far includes:
- https://developer.microsoft.com/en-us/windows/downloads/virtual-machines/ - a development VM with Visual Studio, WSL and Ubuntu; validity limited by calendar date; I assume by that time a newer version of such VM would be published so developers test on freshest rolling platform.
- https://developer.microsoft.com/en-us/microsoft-edge/tools/vms/ - a series of VMs intended for browser testing (matrix of Windows and browser versions) limited by 90 days from first boot
- https://aka.ms/windowsdevelopervirtualmachineeula - rules of engagement (reading needed)
The "fightwarn" effort started in #823 introduced in particular builds of NUT in Windows workers, currently for the sake of seeing if we can do it at all. This can be seen in branches with "fightwarn" in the name, and possibly truncated in scope (to avoid running other test cases while fixing this scenario) by a temporary patch like these from the https://github.com/networkupstools/nut/commits/fightwarn-win branch:
As the latter comment says, the current blocker in this path is the lack of functional autotools which would actually generate the configure script (probably as a .bat or .cmd file, though a posix shell script could work too for that environment).