Rechercher dans la documentation

20 résultats, les meilleurs d'abord

1. php/classes/aDeployTask.md mmo.admin · ligne 417 method MMO\admin\classes\aDeployTask::rollback — Undo this task. Called by the runner, in reverse order, for every task already applied when a later one failed. Must be safe to call on a task that only partially applied.
2. php/tasks/RollbackTask.md mmo.admin · ligne 11 class MMO\admin\tasks\RollbackTask — Go back to a previously shipped release, on purpose (as opposed to @see ActivateTask::rollback, which the runner calls automatically when a deployment fails half-way).
3. php/classes/aDeployTask.md mmo.admin · ligne 344 method MMO\admin\classes\aDeployTask::isRollbackCritical
4. php/classes/aDeployTask.md mmo.admin · ligne 328 method MMO\admin\classes\aDeployTask::isNeeded — Whether this task has anything to do for this target -- e.g. a release already shipped with the same checksum does not need shipping again. A task that returns false is skipped entirely (no apply, no verify, and no rollback if a later task…
5. php/tasks/BackupTask.md mmo.admin · ligne 27 Backups live beside the releases, not inside one, so they survive every deploy, rollback and prune.
6. php/classes/aDeployTask.md mmo.admin · ligne 34 - [`rollback`](aDeployTask.md#adeploytask-rollback) undo it, called by the runner (in reverse order) when a LATER task fails.
7. php/entities/Target.md mmo.admin · ligne 86 | ▪ | 🔐 | [`shared`](#target-shared) | paths (relative to a release) that must NOT be part of a release: they live in `shared/` and are symlinked into every release, so they survive a deploy and a rollback untouched. |
8. php/entities/Target.md mmo.admin · ligne 449 are symlinked into every release, so they survive a deploy and a rollback untouched.
9. php/tasks/ActivateTask.md mmo.admin · ligne 31 It is also the only reversible deploy step: [`rollback`](ActivateTask.md#activatetask-rollback) re-points the link at [`Context::$previous`](../helpers/Context.md#context-previous),
10. deploy.md mmo.admin · ligne 35 single rule is what makes a deploy atomic, a rollback instant, and `git pull` unnecessary.
11. php/entities/Target.md mmo.admin · ligne 527 it), after which every deploy and every rollback is the ordinary `current` swap and this path never moves
12. php/tasks/ShipTask.md mmo.admin · ligne 197 | 🔓 | `isRollbackCritical()` | [`aDeployTask`](../classes/aDeployTask.md#adeploytask) | |
13. php/tasks/RollbackTask.md mmo.admin · ligne 166 | 🔓 | `isRollbackCritical()` | [`aDeployTask`](../classes/aDeployTask.md#adeploytask) | |
14. php/tasks/RollbackTask.md mmo.admin · ligne 169 | 🔓 | `rollback($context)` | [`aDeployTask`](../classes/aDeployTask.md#adeploytask) | Undo this task. Called by the runner, in reverse order, for every task already applied when a later one failed. |
15. php/tasks/ReleaseScriptsTask.md mmo.admin · ligne 253 | 🔓 | `isRollbackCritical()` | [`aDeployTask`](../classes/aDeployTask.md#adeploytask) | |
16. php/tasks/ReleaseScriptsTask.md mmo.admin · ligne 256 | 🔓 | `rollback($context)` | [`aDeployTask`](../classes/aDeployTask.md#adeploytask) | Undo this task. Called by the runner, in reverse order, for every task already applied when a later one failed. |
17. php/tasks/PruneTask.md mmo.admin · ligne 150 | 🔓 | `isRollbackCritical()` | [`aDeployTask`](../classes/aDeployTask.md#adeploytask) | |
18. php/tasks/PruneTask.md mmo.admin · ligne 153 | 🔓 | `rollback($context)` | [`aDeployTask`](../classes/aDeployTask.md#adeploytask) | Undo this task. Called by the runner, in reverse order, for every task already applied when a later one failed. |
19. php/tasks/InstallTask.md mmo.admin · ligne 452 | 🔓 | `isRollbackCritical()` | [`aDeployTask`](../classes/aDeployTask.md#adeploytask) | |
20. php/tasks/InstallTask.md mmo.admin · ligne 455 | 🔓 | `rollback($context)` | [`aDeployTask`](../classes/aDeployTask.md#adeploytask) | Undo this task. Called by the runner, in reverse order, for every task already applied when a later one failed. |

Brancher votre agent