tag:help.appveyor.com,2012-11-13:/discussions/questions/869-deploying-multiple-winows-service-instancesAppVeyor: Discussion 2018-08-25T02:00:07Ztag:help.appveyor.com,2012-11-13:Comment/357739292015-01-14T01:13:34Z2015-01-14T01:13:34ZDeploying Multiple Winows Service Instances<div><p>Hi,</p>
<p>I have a single windows service and I would like to deploy
multiple instances of the same service on one machine, each with
their own configuration file.</p>
<p>Currently, we are using exclusively appveyor agent to deploy to
our own AWS instances. I'm not sure how to approach this problem
using our current setup.</p>
<p>Any advice would be greatly appreciated.</p>
<p>Thank you</p></div>huytag:help.appveyor.com,2012-11-13:Comment/357739292015-01-14T01:31:11Z2015-01-14T01:31:11ZDeploying Multiple Winows Service Instances<div><p>Hm, I see what you mean. You can't have such configuration for
Deployment Agent unless there are multiple similar artifacts, but
with different name.</p>
<p>Alternatively, you can utilize <code>deploy.ps1</code> and,
basically, on deploy copy service package files to multiple
folders, update their <code>service.app.config</code> (or wherever
you store config) and create/update corresponding services (pretty
easy with command line or PowerShell). Configuration could be sent
through environment variables.</p>
<p>Hope that helps.</p>
<p>Other than that we are going to completely revamp Agent
deployment in the coming months and I'll make sure the scenario you
describe is supported.</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/357739292015-01-14T01:40:51Z2015-01-14T01:40:51ZDeploying Multiple Winows Service Instances<div><p>Ah yes, please support multiple deployment and configuration
transform or at least switching. Post deployment scripts &
webhook would also be nice!</p>
<p>We just prefer to keep things transparent with our deployment
tools and not introduce scripts. We're rather use menus and UI for
simplicity; the main reason why we went with appveyor & not
setup our own teamcity + octopus farm.</p></div>huytag:help.appveyor.com,2012-11-13:Comment/357739292015-01-14T03:51:10Z2015-01-14T03:51:10ZDeploying Multiple Winows Service Instances<div><p>OK, I see. Then for now I'd push the same artifact several
times, but with different file names and deployment names (<a href=
"http://www.appveyor.com/docs/build-worker-api#push-artifact">http://www.appveyor.com/docs/build-worker-api#push-artifact</a>).</p>
<p>Deployment Agent became really popular and it's definitely
asking for improvements, especially UI/configuration part.</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/357739292015-09-11T17:15:13Z2015-09-11T17:15:13ZDeploying Multiple Winows Service Instances<div><p>I agree that this is an area I would love to see improvement in.
I have some servers with dozens of apps on them...and in some
cases, dev and production on the same server. This is really
impractical to configure with the agents current limitations.
Essentially, if I have 10 plans all generating artifacts for the
same environment, that's a huge amount of configuration to maintain
in the agent environment settings.</p>
<p>If you could bring those settings into the deployments tab, that
would be incredibly useful. We could then easily use build
conditions and better manage deployment configurations with
multiple plans using the same agent. I would also suggest the
ability to define a before and after powershell script inline on
the interface which run on the agent. I too would like to avoid
going back to the teamcity/bamboo/octopus route...appveyor saved me
from that complexity and cost, but I just need a little bit more to
get all the way there.</p></div>christag:help.appveyor.com,2012-11-13:Comment/357739292015-09-12T00:38:48Z2015-09-12T00:38:48ZDeploying Multiple Winows Service Instances<div><p>Thanks for the suggestions!</p></div>Feodor Fitsner