Environment Variables/Project Variables on Provider Settings for Deployment Agent

tucaz's Avatar


04 May, 2015 11:41 PM


Is it possible to use environment/project variables in provider settings with deployment agent with the Environment deploy functionality?

Right now my artifacts are named like $(APPVEYOR_PROJECT_NAME)_$(APPVEYOR_BUILD_VERSION) (eg. BSP_1.0.0.40) and I would like to pick up this automatically in provider settings like


It works on S3 Environment deploys, but not with Deployment Agent Environment deploys.


  1. Support Staff 1 Posted by Feodor Fitsner on 04 May, 2015 11:45 PM

    Feodor Fitsner's Avatar

    Unfortunately, environment variables are not expanded in setting names. However, it might be an area for further improvements :)

  2. 2 Posted by tucaz on 04 May, 2015 11:53 PM

    tucaz's Avatar

    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.

    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.

    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?

  3. Support Staff 3 Posted by Feodor Fitsner on 05 May, 2015 02:07 AM

    Feodor Fitsner's Avatar

    You can either setup all artifacts under the same environment (provided there are from different projects) or have multiple environments with the same access key.

  4. Ilya Finkelshteyn closed this discussion on 25 Aug, 2018 01:56 AM.

Comments are currently closed for this discussion. You can start a new one.

Keyboard shortcuts


? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac