tag:help.appveyor.com,2012-11-13:/discussions/questions/1255-environment-variablesproject-variables-on-provider-settings-for-deployment-agentAppVeyor: Discussion 2018-08-25T01:56:06Ztag:help.appveyor.com,2012-11-13:Comment/367492812015-05-04T23:45:28Z2015-05-04T23:45:28ZEnvironment Variables/Project Variables on Provider Settings for Deployment Agent<div><p>Unfortunately, environment variables are not expanded in setting
names. However, it might be an area for further improvements :)</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/367492812015-05-04T23:53:50Z2015-05-04T23:53:50ZEnvironment Variables/Project Variables on Provider Settings for Deployment Agent<div><p>Hmmmm... that's unfortunate. I'm looking at the Environment
deploy functionality (out of the project) to be a general
deployment setting to be reused across projects.</p>
<p>Right now I have a S3 Environment configured and a Deployment
Agent environment. My goal is to use them to deploy to whenever
environment I want for each project I have and that's why variables
would come in hand.</p>
<p>Since every deploy generates an artifact with a different name
what would be your recommendation regarding usage of Environments?
Is there any best-practice to achieve what I'm looking for?</p></div>tucaztag:help.appveyor.com,2012-11-13:Comment/367492812015-05-05T02:07:18Z2015-05-05T02:07:26ZEnvironment Variables/Project Variables on Provider Settings for Deployment Agent<div><p>You can either setup all artifacts under the same environment
(provided there are from different projects) or have multiple
environments with the same <em>access key</em>.</p></div>Feodor Fitsner