[test] Okay, let's use the fauly spec literally

Test with multiple Python versions
In particular, runners and Node.js seems to be failing with Python 2. We'd better test those to see if they ever break on us.
2026-09-07 06:07:19 +08:00 · 2020-02-11 23:51:18 +02:00 · 2020-02-11 23:47:59 +02:00 · 2020-02-11 23:43:32 +02:00 · 2020-02-11 23:42:24 +02:00 · 2020-02-11 23:37:34 +02:00
3 changed files with 55 additions and 2 deletions
@@ -0,0 +1,11 @@
+name: Python package
+on: [push]
+jobs:
+  build:
+    runs-on: "windows-latest"
+    strategy:
+      matrix:
+        python-version:
+          - "2.7"
+    steps:
+    - uses: ilammy/msvc-dev-cmd@v1
@@ -6,15 +6,23 @@ on:
    branches:
      - master
      - release/*
+      - wip/debugging
+  schedule:
+    - cron: '0 6 * * *'

 jobs:
  test:
    name: default
-    runs-on: ${{ matrix.os }}
+    runs-on: windows-latest
    strategy:
      fail-fast: false
      matrix:
-        os: [windows-2016, windows-2019, windows-latest]
+        python-version:
+          - '2.7'
+          - '3.5'
+          - '3.6'
+          - '3.7'
+          - '3.8'
    steps:
      - name: Check out source code
        uses: actions/checkout@v1
@@ -23,6 +31,7 @@ jobs:
      - name: Enable Developer Command Prompt
        uses: ./
      - name: Compile and run some C code
+        shell: cmd
        run: |
          cl.exe hello.c
          hello.exe
@@ -0,0 +1,33 @@
+name: msvc-dev-cmd (release)
+
+on:
+  push:
+    branches:
+      - release/*
+      - wip/debugging
+  schedule:
+    - cron: '0 6 * * *'
+
+jobs:
+  test:
+    name: release
+    runs-on: windows-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        python-version:
+          - '2.7'
+          - '3.5'
+          - '3.6'
+          - '3.7'
+          - '3.8'
+    steps:
+      - name: Setup Developer Command Prompt
+        uses: ilammy/msvc-dev-cmd@v1
+      - name: Check out source code
+        uses: actions/checkout@v1
+      - name: Compile and run some C code
+        shell: cmd
+        run: |
+          cl.exe hello.c
+          hello.exe
Author	SHA1	Message	Date
ilammy	e9437d41fc	[test] Okay, let's use the fauly spec literally	2020-02-11 23:51:18 +02:00
ilammy	5cf1eeecd8	Test with multiple Python versions In particular, runners and Node.js seems to be failing with Python 2. We'd better test those to see if they ever break on us.	2020-02-11 23:47:59 +02:00
ilammy	060bdc7cb5	[debug] add self-test	2020-02-11 23:43:32 +02:00
ilammy	b6e52219de	Integration test for release version Make sure that the released version is also fine. Run this test every time a push is made into the release branch as well as on schedule.	2020-02-11 23:42:24 +02:00
ilammy	a46bb485fb	Use cmd.exe as shell It works well and we don't need PowerShell which has weird notion of default executable search path.	2020-02-11 23:37:34 +02:00
ilammy	ce962cf525	[debug] add self-test	2020-02-11 23:33:09 +02:00
ilammy	987899132c	Run test job at 06:00 every day Well, it seems the environment is changing so we'd better run the tests reguarly to see whether something breaks in a timely manner. GitHub Actions also don't offer other Windows environments now, only windows-latest is available. Reduce test matrix to only that.	2020-02-11 23:27:51 +02:00