tag:help.appveyor.com,2012-11-13:/discussions/questions/3415-is-it-possible-to-have-multiple-appveyoryml-configurationsAppVeyor: Discussion 2018-08-25T02:15:35Ztag:help.appveyor.com,2012-11-13:Comment/421202942017-03-09T19:20:42Z2017-03-09T19:20:42ZIs it possible to have multiple appveyor.yml configurations?<div><p>Hi Ewout,</p>
<p>I would do the following:</p>
<ul>
<li>Create separate AppVeyor projects for FrontEnd and BackEnd. You can target the same repository from different projects and use separate YAML files with custom name as described <a href="https://www.appveyor.com/docs/build-configuration/#configuring-build">here</a></li>
<li>Make FrontEnd build call BackEnd build as <code>on_success</code> script from PowerShell using <a href="https://www.appveyor.com/docs/api/">API</a>. <a href="https://gist.github.com/IlyaFinkelshteyn/89d19593318276e2538040787bc4fce7">Here</a> is PowerShell sample</li>
<li>You can run this start build script conditionally if BackEnd .NET solution is available. You can simple check it with <code>test-path</code> (if I understand what does 'available' means correctly).</li>
</ul>
<p>There are still few open questions common for this kind of chaining:</p>
<ul>
<li>What kind of change should trigger FrontEnd build?</li>
<li>Should BackEnd build be triggered by some change or only by FrontEnd build?</li>
<li>Should FrontEnd build wait for BackEnd build to finish successfully and fail if BackEnd build is not happy?</li>
</ul>
<p>--ilya.</p></div>Ilya Finkelshteyn