You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently there are log line produced for each stage of the deployment lifecycle, however there is nothing reported at the end of deploy. It would be great to get a message like:
Given the last stage of the deploy is often "verify", I've run into logs ending like this:
[2019-07-11 16:33:52.787] [d-BO8Z62ZIB]Script - remote_scripts/validate_service.sh
[2019-07-11 16:33:52.893] [d-BO8Z62ZIB][stdout]Waiting for http service
From which you can't really tell whether the deployment completed, or is it still hanging on the waiting step.
This can be of course worked around by adding completion messages to all scripts, but given this requires extra attention in every single deploy process, could we get one from the codedeploy agent instead?
The text was updated successfully, but these errors were encountered:
Currently there are log line produced for each stage of the deployment lifecycle, however there is nothing reported at the end of deploy. It would be great to get a message like:
Given the last stage of the deploy is often "verify", I've run into logs ending like this:
From which you can't really tell whether the deployment completed, or is it still hanging on the waiting step.
This can be of course worked around by adding completion messages to all scripts, but given this requires extra attention in every single deploy process, could we get one from the codedeploy agent instead?
The text was updated successfully, but these errors were encountered: