tag:help.appveyor.com,2012-11-13:/discussions/questions/52669-run-parallel-builds-on-the-same-os-using-different-build-scriptsAppVeyor: Discussion 2021-11-24T20:07:37Ztag:help.appveyor.com,2012-11-13:Comment/489965562021-01-27T01:30:22Z2021-01-27T01:30:22ZRun Parallel Builds on the Same OS Using Different Build Scripts<div><p>Do you have some appveyor.yml already?</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/489965562021-11-24T20:00:20Z2021-11-24T20:07:37ZRun Parallel Builds on the Same OS Using Different Build Scripts<div><p>Sorry for taking so long to get back to you. I must have missed that someone responded.</p>
<p>Here's my appveyor.yml [1].</p>
<p>What I want is at total of 7 jobs:</p>
<ul>
<li>2 jobs only on Visual Studio 2013 Visual Studio 2015 that run a build under Windows PowerShell (i.e. <code>ps</code>).</li>
<li>5 jobs on all images except Visual Studio 2013 that run the build under PowerShell (i.e. <code>pwsh</code>).</li>
</ul>
<p>Currently, with this YAML, I get <a href="https://ci.appveyor.com/project/WebMD-Health-Services/whiskey/builds/41657971">six jobs</a> and macOS, Ubuntu, Visual Studio 2015, and Visual Studio 2022 propertly run PowerShell (i.e. <code>pwsh</code>), Visual Studio 2013 properly runs Windows PowerShell (i.e. <code>ps</code>), but I get only one Visual Studio 2019 job and it runs Windows PowerShell (i.e. <code>ps</code>). I expect there to be a second Visual Studio 2019 job that runs on PowerShell (i.e. <code>pwsh</code>).</p>
<p>[1]</p>
<pre>
<code>image:
- macOS
- Ubuntu
- Visual Studio 2013
- Visual Studio 2015
- Visual Studio 2019
- Visual Studio 2022
for:
- matrix:
only:
- image: Visual Studio 2013
- image: Visual Studio 2019
build_script:
- ps: $PSVersionTable ; .\build.ps1
- matrix:
except:
- image: Visual Studio 2013
build_script:
- pwsh: $PSVersionTable ; ./build.ps1</code>
</pre></div>splatteredbits