aboutsummaryrefslogtreecommitdiffhomepage
path: root/tasks/deploy.yml
Commit message (Collapse)AuthorAgeFilesLines
* Bump clever waiting time to 1 hourAntoine Vandecreme2021-06-031-3/+3
|
* deploy: try to restart the app when the CLI asks to do itPaul Bonaud2020-08-061-0/+7
| | | | | | | | | | | | | | | 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.
* Add support for linking service dependenciesClement Delafargue2020-07-021-0/+6
|
* Don't run `clever deploy` if the app is up-to-dateClement Delafargue2020-06-301-1/+1
| | | | | | | | | | | 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 outPaul Bonaud2020-06-291-1/+1
|
* Add support for scalability configurationClement Delafargue2020-06-221-0/+14
| | | | Closes #52
* Inline `clever scale --build-flavor` commandClement Delafargue2020-06-191-2/+1
|
* Add optional build flavor configurationClement Delafargue2020-06-191-0/+9
|
* Use JSON import for environment variablesClement Delafargue2020-06-191-1/+1
| | | | | | | | 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 usPaul Bonaud2020-06-171-55/+20
| | | | | See recent changes (https://github.com/CleverCloud/clever-tools/pull/415) introduced in 2.5.0+ version of the clever cli tools
* deploy: add a timeout in the polling waiting scriptPaul Bonaud2019-08-011-2/+13
|
* deploy: revert back to git push + pollingPaul Bonaud2019-07-311-61/+32
| | | | | | | | | | | | | | | | In #19 we removed the polling script to rely on the clever cli's ability to wait on `clever deploy` command. After more than 6 months of experimentation it seems the command is still not reliable (sometimes the command never returns, sometimes it returns even when the deployment has finished..). Thus we are reverting back to our manual process of polling `clever activity` every 5 seconds. The timeout for this polling is set at the Ansible level (not in the bash script) and set for 40 minutes. This should give enough time for any of our applications to deploy.
* fix(deploy): fail the task correctly when last deploymt failedPaul Bonaud2019-05-131-3/+5
|
* Missing /Gaëtan Duchaussois2019-02-221-1/+1
|
* linitingGaëtan Duchaussois2019-02-211-3/+7
|
* use full path for clever helper invocationGaëtan Duchaussois2019-02-211-2/+2
|
* deploy: check "up-to-date" error to succeeded if last commit is OKPaul Bonaud2019-01-161-1/+35
|
* fix: Fail module takes one argumentPaul Bonaud2019-01-141-1/+2
|
* deploy_task: Update clever CLI tools and use it instead of git pushPaul Bonaud2019-01-141-26/+33
| | | | | | | | Updating to latest version of 1.1.1 helps to have a stable `clever deploy` command. This commit relies on the output of the command instead of manually pooling the results with `clever activity` command.
* fix(deploy): Yet again a missing chdir to execute from app rootPaul Bonaud2018-11-301-1/+3
|
* fix(deploy): Make sure to execute clever commands in app_root dirPaul Bonaud2018-11-301-0/+6
|
* Revert "Merge pull request #19 from paulrbr-fl/update-clever-tools"Paul Bonaud2018-11-301-29/+24
| | | | | This reverts commit 695ceaa28821660e17a1cf819cffebe1b5d8c7ca, reversing changes made to 5485dbc4db3e141673457475bcda5fc88057739f.
* Revert "Merge pull request #20 from paulrbr-fl/update-clever-tools"Paul Bonaud2018-11-301-2/+1
| | | | | This reverts commit b17a839d622bdb36ddbe2e0667559c33e9b7fd8a, reversing changes made to 695ceaa28821660e17a1cf819cffebe1b5d8c7ca.
* fix: Fail module takes one argumentPaul Bonaud2018-11-211-1/+2
|
* deploy_task: Update clever CLI tools and use it instead of git pushPaul Bonaud2018-11-211-24/+29
| | | | | | | | Updating to latest version of 1.1.1 helps to have a stable `clever deploy` command. This commit relies on the output of the command instead of manually pooling the results with `clever activity` command.
* fix: 😬 really fix the usage of "clever_app_root" when waiting deployPaul Bonaud2018-11-051-1/+1
| | | | | | | Followup after the fix of #15 it was still missing another case of "git" usage. This should be the last fix about this variable 🤞.
* fix: clever_app_root is provided & exec is outside of "parent dir"Paul Bonaud2018-11-051-0/+6
| | | | | | | | | | | | Imagine such a usecase: - project is in `/project` - executing Ansible in `/ansible` with `clever_app_root: /project` will fail deploying with the git push with the following error: ``` Not a git repository (or any of the parent directories): .git" ``` This PR fixes this.
* vars: add a clever_syslog_server variable replacing syslog_serverPaul Bonaud2018-10-041-2/+2
| | | | | All variables "namespaced" with the role name is helpful to read "client" configurations
* domain: allow the domain to be specified via clever_domain variablePaul Bonaud2018-09-281-2/+2
| | | | | | | | Every other variables are prefixed with `clever_` which makes the definition of variables clearer from a "app" configuration point of view. WDYT?
* deploy: Make sure repo is unshallow copy before pushing to cleverPaul Bonaud2018-09-211-0/+16
| | | | | | | | If your build tool only uses a shallow clone of your project, Clever cloud will fail on first time git push. You need to git push a full clone of your git repo for the first time deployment to clever. This PR fixes that.
* add ansible-lint test and fix warningGaëtan Duchaussois2018-09-211-0/+6
|
* Watch and wait for CleverFrédéric Menou2018-03-301-1/+13
|
* Migrating single tasks file to a galaxy roleGaëtan Duchaussois2018-02-221-0/+30
generated by cgit v1.2.3 (git 2.25.1) at 2024-06-10 04:45:19 +0000