summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAndres Freund <andres@anarazel.de>2023-02-02 21:31:48 -0800
committerAndres Freund <andres@anarazel.de>2023-02-02 21:31:48 -0800
commit8488babc7f497949f89f77c1b18e41e0962e5398 (patch)
tree958aa2778075ce40d8d92f8969474b3065da61d8
parent83c7e2f2a2f541b5adc11c9d2826eeaf2a22361a (diff)
ci: Use windows VMs instead of windows containers
So far we have used containers for testing windows on cirrus-ci. Unfortunately they come with substantial overhead: First, the container images are pulled onto the host on-demand. Due to the large size of windows containers, that ends up taking nearly 4 minutes. Secondly, IO is slow, leading to CI runs taking long. Thus switch to windows VMs, improving windows CI times by well over 2x. Author: Nazir Bilal Yavuz <byavuz81@gmail.com> Discussion: https://postgr.es/m/211afb88-6df6-b74d-f1b7-84b5f21ad875@gmail.com Backpatch: 15-, where CI was added
-rw-r--r--.cirrus.yml6
1 files changed, 4 insertions, 2 deletions
diff --git a/.cirrus.yml b/.cirrus.yml
index 3bd806b0183..f0d1b3ec9e9 100644
--- a/.cirrus.yml
+++ b/.cirrus.yml
@@ -400,8 +400,10 @@ task:
only_if: $CIRRUS_CHANGE_MESSAGE !=~ '.*\nci-os-only:.*' || $CIRRUS_CHANGE_MESSAGE =~ '.*\nci-os-only:[^\n]*windows.*'
- windows_container:
- image: $CONTAINER_REPO/windows_ci_vs_2019:latest
+ compute_engine_instance:
+ image_project: $IMAGE_PROJECT
+ image: family/pg-ci-windows-ci-vs-2019
+ platform: windows
cpu: $CPUS
memory: 4G