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
terminus site deploy should exit with a non-zero status if deploy fails.
Actual behavior
Here are two snippets from a script which execs terminus site deploy and then checks the exit status. In these two cases the exit status was 0, but the log level was "error".
terminus site deploy --site=upgrade-testing-0110-diversity-ob-dl-02 --env=live --cc --updatedb --note="Deployed by klu via /usr/local/bin/istdrupal-updates-apply" --format=json
date: 2016-11-17 01:28:08
level: ERROR
message: cURL error 7: Failed to connect to terminus.pantheon.io port 443: Connection refused (see http://curl.haxx.se/libcurl/c/libcurl-errors.html)
terminus site hostnames list --site=optometry-ob --env=live
Would you like to deploy code from Test to live? (y/n): y
terminus site deploy --site=optometry-ob --env=live --cc --updatedb --note="Deployed by annagaz via /usr/local/bin/istdrupal-updates-apply" --format=json
date: 2016-11-18 22:08:53
level: ERROR
message: Successfully queued converge_appserver_binding
Steps to reproduce the behavior
Apologies, but I couldn't find a way to reproduce this. I tried creating a TCP error, but got a different message.
Perhaps the timestamps, site names and messages will be useful in tracking down these conditions. If not, I understand. Just thought it might be worth reporting.
The text was updated successfully, but these errors were encountered:
Version
0.13.3
Expected behavior
terminus site deploy should exit with a non-zero status if deploy fails.
Actual behavior
Here are two snippets from a script which execs
terminus site deploy
and then checks the exit status. In these two cases the exit status was 0, but the log level was "error".Steps to reproduce the behavior
Apologies, but I couldn't find a way to reproduce this. I tried creating a TCP error, but got a different message.
Perhaps the timestamps, site names and messages will be useful in tracking down these conditions. If not, I understand. Just thought it might be worth reporting.
The text was updated successfully, but these errors were encountered: