tag:help.appveyor.com,2012-11-13:/discussions/questions/7500-can-a-project-web-deploy-asap-to-website-1-but-also-allow-a-manual-deployment-to-website-2-later-onAppVeyor: Discussion 2018-08-25T02:19:25Ztag:help.appveyor.com,2012-11-13:Comment/432497282017-08-21T03:11:14Z2017-08-21T03:11:27ZCan a project web deploy asap (to website #1) but also allow a manual deployment (to website #2) later on?<div><p>Environments where created with intention to decouple deployment from build. So you can redeploy the same "green" bits to different environment. So yes, Environments is right way.</p>
<p>But why don't you simple use <a href="https://docs.microsoft.com/en-us/azure/app-service-web/web-sites-staged-publishing">deployment slot swap</a>? With it I believe you do not need second deployment.</p></div>Ilya Finkelshteyntag:help.appveyor.com,2012-11-13:Comment/432497282017-08-21T03:23:04Z2017-08-21T03:23:04ZCan a project web deploy asap (to website #1) but also allow a manual deployment (to website #2) later on?<div><p>We do. We have two different physical web apps and we deploy to the staging slot of each.</p>
<p>website #1 -> straight away with provider: webdeploy<br>
website #2 -> we want to do this manually.</p>
<p>So if we are to use Environments, how would we go about using the artifact from the build get pushed to the Environment?</p></div>Pure Krometag:help.appveyor.com,2012-11-13:Comment/432497282017-08-21T03:52:18Z2017-08-21T03:52:18ZCan a project web deploy asap (to website #1) but also allow a manual deployment (to website #2) later on?<div><p>When you start environment deployment with UI, you are presented with the list of builds. If you choose specific build, artifact from that specific build will be deployed.</p></div>Ilya Finkelshteyntag:help.appveyor.com,2012-11-13:Comment/432497282017-08-21T04:00:17Z2017-08-21T04:00:17ZCan a project web deploy asap (to website #1) but also allow a manual deployment (to website #2) later on?<div><p>Ok, so this means we need to manually add an <code>artifact</code> section to the yml? and if yes, what do we need to zip up for an ASP.NET 4.x website?</p>
<p>something like:</p>
<ul>
<li>path: MyProjectFolder\bin\$(configuration) name: website.zip</li>
</ul>
<p>and this artifact will be web deployed in the environment?</p></div>Pure Krometag:help.appveyor.com,2012-11-13:Comment/432497282017-08-21T04:09:09Z2017-08-21T04:09:09ZCan a project web deploy asap (to website #1) but also allow a manual deployment (to website #2) later on?<div><p>If given build already has successful deployment to staging, this means that artifacts were already packaged, isn't it? You can find artifact specific you given build in <code>Artifacts</code> tab for that build. Probably artifact was published implicitly with <code>publish_wap: true</code> ...</p></div>Ilya Finkelshteyntag:help.appveyor.com,2012-11-13:Comment/432497282017-08-25T03:41:58Z2017-08-25T03:41:58ZCan a project web deploy asap (to website #1) but also allow a manual deployment (to website #2) later on?<div><p>Correct. Artifact was published implicitly with WAP true.</p>
<p>Webdeploy to Azure worked.<br>
Nothing to Environment worked.</p>
<p>Environment output:<br>
<code>No artifacts were uploaded. Make sure you have specified correct artifacts filter.</code></p>
<p>So do i need to:</p>
<ol>
<li><code>publish_wap: false</code><br></li>
<li>create/add the <code>artifact:</code> section and specify the aspnet bin dir which has to be zipped up<br></li>
<li>specify this artifact in BOTH webdeploy and environment</li>
</ol>
<p>Lastly - when we use ENVIRONMENT .. it does the deploy straight away. Is it possible to <em>NOT</em> deploy asap ... but wait until we manually click some button somewhere (e.g. the <code>new deployment</code> button/link).</p></div>Pure Krometag:help.appveyor.com,2012-11-13:Comment/432497282017-08-25T09:56:16Z2017-08-25T09:56:16ZCan a project web deploy asap (to website #1) but also allow a manual deployment (to website #2) later on?<div><p>Please send us your build configuration in YAML format and Environment settings screenshot. Feel free to delete all secrets and make this thread private if you wish.</p>
<p>I am not sure I fully understood second question. Environment deploys ASAP if you call it from the build. But you can start Environment deployment manually, from Environment UI, right?</p></div>Ilya Finkelshteyn