Andrey Lushnikov
36b87000e4
chore(ci): remove Win from Cirrus builds ( #2689 )
...
Remove Cirrus Win targets until there's a good resolution.
Postmortem:
- CirrusCI uses [Windows Server
Containers](https://docs.microsoft.com/en-us/virtualization/windowscontainers/about/#windows-container-types ) to run windows builds.
- Windows Server Containers don't include all the libraries that are required to run general application. See [msdn discussion](https://social.msdn.microsoft.com/Forums/en-US/a50e7dd7-c73f-45e0-89b4-92ba3ad2bcda/ieframedll-and-shdocvwdll-are-missing-from-windowsservercore-image?forum=windowscontainers ).
- A recent [chromium commit](https://crrev.com/560677 ) added win dependencies missing in Windows Server Containers.
We'll be able to bring back Win builds on Cirrus once the full-fledged
Win containers are released (announced
[recently](https://channel9.msdn.com/Events/Build/2018/BRK2149 ).
2018-06-06 20:11:22 -05:00
Andrey Lushnikov
4bc23319a2
chore(ci): temporary disable cirrus win builds ( #2666 )
...
Win bots all fail on Cirrus; disable them until the issue is resolved.
We still have win coverage with AppVeyour.
2018-06-02 11:45:14 -07:00
Fedor Korotkov
85d5a3348c
chore(ci): switch Windows containers ( #2662 )
...
Cirrus CI got some optimizations for containers based of `microsoft/windowsservercore:latest`.
Now startup time for windows builds is around 1:30 seconds instead of around 4 minutes.
to: @aslushnikov
2018-06-01 15:15:16 -07:00
Fedor Korotkov
554bd59588
chore(CI): add experimental Cirrus CI ( #2181 )
...
This patch adds experimental support for Cirrus CI builds.
Cirrus CI has both Windows and Linux, uses google cloud and runs builds
in Docker containers.
This seems to be a promising combination for our needs.
2018-03-13 08:06:40 -07:00
