-
Notifications
You must be signed in to change notification settings - Fork 186
[Windows] Agent silently hangs forever if hook script doesn't close STDOUT #288
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I have run in to the same issue, any updates on this? |
I developed a workaround using PowerShell, as far as I know this bug has not been fixed:
|
Does this fix the issue https://stackoverflow.com/questions/42222004/run-exe-in-background |
This is what worked for me create a script name also for some reason, this only works if I invoke using command line Just another note: |
Closing as not planned. You need to start your application in a process other than the one CodeDeploy is using to run your hook script. |
On Windows I need the CodeDeploy Agent to simply start a plain
.exe
(non-service) process on the server for theApplicationStart
, but this does not seem to be possible. It seems to be related to how the Agent runs the deployment scripts, similar issues here.However, the problem doesn't seem to have ever been fixed, and the only workarounds I can find are for Linux (the AWS documentation also only provides work around examples for Linux).
I have a script that invokes the server process in what should be a non-blocking way, it works fine when running the script from the command line:
start.bat
Output:
I've also tried these but they don't work:
What's really annoying is that the process gets created but the Agent still reports the deployment as a failure.
The text was updated successfully, but these errors were encountered: