tag:help.appveyor.com,2012-11-13:/discussions/questions/665-trigger-only-debug-build-not-releaseAppVeyor: Discussion 2018-10-19T08:16:50Ztag:help.appveyor.com,2012-11-13:Comment/351967802014-11-06T22:25:12Z2014-11-06T22:25:12ZTrigger only Debug build, not Release<div><p>Branches are definitely better as you are having the same build
number for both debug and release builds.</p>
<p>Another way is to setup two projects <code>MyApp - debug</code>
and <code>MyApp - release</code> that could be treated as TC build
configurations. For release project you just remove webhook from
repo to disable building on push.</p>
<p>Yet another way could be a single project, where you have some
<code>Release=true|false</code> environment variable distinguishing
build flows. By default, in your <code>appveyor.yml</code> you
could have 'Release=false<code>defined and then when you are
releasing you set</code>Release=true` on UI - it will override the
one defined in YML.</p>
<p>Let me know if you have any questions.</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/351967802014-11-11T08:51:39Z2014-11-11T08:51:39ZTrigger only Debug build, not Release<div><p>Thanks Feodor - moving to branches is the "right" thing to do,
but will require a change (albeit for the better) to our
workflow.</p>
<p>Phil</p></div>Phil Dye