| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
| |
`grep -v` makes sure a file contains other lines than the one that
matched. This is different from `! grep` which makes sure the file
does not contain a line that matched.
|
|
|
|
|
| |
Previously, only the commands not directly handled by the stub were
logged. We want to log all commands instead
|
|
|
|
|
| |
It makes sure `clever deploy` is _not_ called if the application
is up-to-date on clever cloud
|
| |
|
| |
|
| |
|
|
|
|
| |
They make sure that ansible does not crash while calling `clever scale`
|
| |
|
|
|
|
|
| |
See recent changes (https://github.com/CleverCloud/clever-tools/pull/415)
introduced in 2.5.0+ version of the clever cli tools
|
|
|
|
|
|
| |
The `CC_RUN_COMMAND` variable was defined in case we use haskell
binary as entrypoints. However if the `clever_haskell_entry_point`
variable is not defined we shouldn't define the `CC_RUN_COMMAND` env variable.
|
|
|