APPLICATION_PATH env var is one artifact behind in `before-deploy.ps1`
I have one server with the deployment agent watching for
deployments. That server is currently the home for several
services. I have one environment where my builds send their
artifacts. These are several artifacts and I have each set up to
deploy to the environment. Each artifact deployment has a
before-deploy.ps1 and a deploy.ps1. All
the deploy.ps1 files work as expected. However, all
the before-deploy.ps1 scripts use the
APPLICATION_PATH from the previous artifact.
Write-Host "Starting the current adapter..."
& "$Env:APPLICATION_PATH\Project.Accounts.Commands.Host.exe" start
... but $Env:APPLICATION_PATH is not the path of
this artifact... it's the path of the artifact that just finished
deploying. Thoughts?
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
| ? | 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
Support Staff 1 Posted by Feodor Fitsner on 28 Jul, 2015 10:53 PM
Will take a look.
What kind of application/artifact is that?
2 Posted by byron on 28 Jul, 2015 10:55 PM
It's a console app that uses TopShelp to install as a windows service.
Support Staff 3 Posted by Feodor Fitsner on 29 Jul, 2015 12:08 AM
The issue has been found and fixed.
Please re-install Deployment Agent: http://www.appveyor.com/downloads/AppveyorDeploymentAgent.msi
Let me know about the results.
Ilya Finkelshteyn closed this discussion on 25 Aug, 2018 01:58 AM.