Use matrix strategy.

Author: pablorcum

.github/workflows/main.yml

@@ -1,8 +1,5 @@
 name: CI
 
-env:
-  MATLAB_VER: R2023a
-
 # Controls when the workflow will run
 on:
   # Triggers the workflow on push or pull request events but only for the "master" branch
@@ -22,6 +19,10 @@ on:
 # A workflow run is made up of one or more jobs that can run sequentially or in parallel
 jobs:
   check:
+    strategy:
+      fail-fast: false # Run with every MATLAB version independently
+      matrix:
+        matlabVer: [R2023a] # List of MATLAB releases to test
     runs-on: matlab
     # Steps represent a sequence of tasks that will be executed as part of the job
     steps:  
@@ -41,7 +42,7 @@ jobs:
 
       - name: Run MATLAB command
         run: |
-          &"$env:ProgramFiles\MATLAB\$env:MATLAB_VER\bin\matlab.exe" -batch "openProject(pwd); cd('buildUtilities'); buildtool check"
+          &"$env:ProgramFiles\MATLAB\${{ matrix.matlabVer }}\bin\matlab.exe" -batch "openProject(pwd); cd('buildUtilities'); buildtool check"
 
       - name: Archive check results
         uses: actions/upload-artifact@v3
@@ -51,6 +52,10 @@ jobs:
           path: checkResults.json
 
   test:
+    strategy:
+      fail-fast: false # Run with every MATLAB version independently
+      matrix:
+        matlabVer: [R2023a] # List of MATLAB releases to test
     runs-on: matlab
     # Steps represent a sequence of tasks that will be executed as part of the job
     steps:  
@@ -75,7 +80,7 @@ jobs:
 
       - name: Run MATLAB command
         run: |
-          &"$env:ProgramFiles\MATLAB\$env:MATLAB_VER\bin\matlab.exe" -batch "openProject(pwd); cd('buildUtilities'); buildtool test({'noHW','bdConnected'})"
+          &"$env:ProgramFiles\MATLAB\${{ matrix.matlabVer }}\bin\matlab.exe" -batch "openProject(pwd); cd('buildUtilities'); buildtool test({'noHW','bdConnected'})"
 
       - name: Publish Test Results
         uses: EnricoMi/publish-unit-test-result-action/composite@v2