| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
This commit also upgrades the nix channel used in the CI to be able to
test with Dhall v1.34.0
|
| |
|
|\
| |
| | |
travis: Use encrypted token for slack notification
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This encrypts the token used to talk with Slack (with a new generated
token and the old one has been revoked)
Encrypted using the repository key with the `travis` CLI:
```
travis encrypt "<user>:<token>" --add notifications.slack.rooms
```
cf documentation
https://docs.travis-ci.com/user/notifications/#configuring-slack-notifications
About #66
|
|\
| |
| | |
Prepare for open-source: adding license and clarification in README
|
| |
| |
| | |
Co-authored-by: Clément Delafargue <39330590+clementd-fretlink@users.noreply.github.com>
|
|/
|
|
| |
About #66
|
|\
| |
| | |
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.
|
|\
| |
| | |
Service dependencies
|
| | |
|
| | |
|
| | |
|
|/ |
|
|\
| |
| | |
don't run `clever deploy` if the app is up-to-date
|
| |
| |
| |
| |
| |
| | |
`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
|
| | |
|
|/
|
|
|
|
|
|
|
|
|
| |
Running `git push` when the remote is up-to-date
no-ops (it does not trigger a deployment, but it does not fail either).
Running `clever deploy` when the remote is up-to-date triggers a failure. Here, we care about the _end result_ (ie the app is deployed on the correct commit), so no-oping is more appropriate.
This behaviour is not baked in `clever-tools`, but I think it should. I opened an issue. This script
is a temporary workaround. (at least I hope it's temporary)
https://github.com/CleverCloud/clever-tools/issues/422
|
|\
| |
| | |
fix: prevent crash when the deployment times out
|
| |
| |
| |
| |
| |
| | |
NIX_PATH used to be enough to select the channel to use, but as Travis
add the nixpkgs-unstable channel we can get unexpected results when
nix decides to push a new unstable version out there in the public.
|
|/ |
|
|\
| |
| | |
dhall: add missing configuration for clever_restart_only variable
|
|/
|
|
| |
This change was forgotten in #70
|
|\
| |
| | |
feature: add a new 'clever_restart_only' flag to restart an app
|
| | |
|
| | |
|
|/
|
|
|
| |
This new flag will perform a restart on the target clever cloud
application instead of deploying it.
|
|\
| |
| | |
core: README cleanup and test env cleanup
|
| | |
|
|/
|
|
| |
Part of #66
|
|\
| |
| | |
scalability configuration
|
| |
| |
| |
| | |
They make sure that ansible does not crash while calling `clever scale`
|
|/
|
|
| |
Closes #52
|
|\
| |
| | |
fix: make sure not to include unecessary ENV variable
|
| |
| |
| |
| |
| |
| |
| | |
This is a fix to an unfortunate bug introduced by #64 because we had a
default value set to `None` on the
`clever_haskell_entry_point`. Ansible considers `None` as a defined
value so the `is defined` condition doesn't match our need
|
| | |
|
|/ |
|
|\
| |
| | |
Add optional build flavor configuration
|
| |
| |
| | |
Co-authored-by: paulrbr-fl <43074087+paulrbr-fl@users.noreply.github.com>
|
| | |
|
| | |
|
|/ |
|
|\
| |
| | |
Use JSON import for environment variables
|
| | |
|
|/
|
|
|
|
|
|
| |
The env can be provided as a JSON list `[{"name": "PORT", "value": "8080"}]`.
The `dict2items` filter provided by ansible is _almost_ what we want, but it
keeps the value original types (a boolean is kept as a boolean in the JSON value).
Since environment variables are strings and `clever-tools` does not want to make
the implicit coercion for us, we need to do it ourselves.
|
|\
| |
| | |
deploy: remove custom polling script now that the CLI does it for us
|
|/
|
|
|
| |
See recent changes (https://github.com/CleverCloud/clever-tools/pull/415)
introduced in 2.5.0+ version of the clever cli tools
|
|\
| |
| | |
fix: there was a bug in the generate env file
|