aboutsummaryrefslogtreecommitdiffhomepage
path: root/tests/test-noop-deploy.yml
diff options
context:
space:
mode:
authorPaul Bonaud <paul.bonaud@fretlink.com>2020-08-06 11:44:26 +0200
committerPaul Bonaud <paul.bonaud@fretlink.com>2020-08-06 15:54:27 +0200
commitc3e2ff5e0f31c61eae330a1a41d7a8a83435d9bd (patch)
treef03e1db57031f574657838a8a15c41319b1c18be /tests/test-noop-deploy.yml
parent315c7f51af48b54719bd793d9d28a4bb396a926a (diff)
downloadansible-clever-c3e2ff5e0f31c61eae330a1a41d7a8a83435d9bd.tar.gz
ansible-clever-c3e2ff5e0f31c61eae330a1a41d7a8a83435d9bd.tar.zst
ansible-clever-c3e2ff5e0f31c61eae330a1a41d7a8a83435d9bd.zip
deploy: try to restart the app when the CLI asks to do it
In some cases (rollback or deployment errored on clever side), clever-tools will fail when calling `clever deploy` because it thinks the currently being deployed commit is already deployed. However in some cases the git pushed commit is not the currently running commit. Leading to a failure in our deployment process. The proposed solution from the clever tools error is to launch `clever restart`. Until we wait for https://github.com/CleverCloud/clever-tools/issues/422 to be fixed, let's do what the error message say: try to restart in case of a deployment failure.
Diffstat (limited to 'tests/test-noop-deploy.yml')
0 files changed, 0 insertions, 0 deletions