fix: set deployment failed if new container is not healthy
This commit is contained in:
parent
ea271ca079
commit
53965ab8ed
1 changed files with 3 additions and 0 deletions
|
|
@ -1295,6 +1295,9 @@ private function stop_running_container(bool $force = false)
|
|||
});
|
||||
} else {
|
||||
$this->application_deployment_queue->addLogEntry("New container is not healthy, rolling back to the old container.");
|
||||
$this->application_deployment_queue->update([
|
||||
'status' => ApplicationDeploymentStatus::FAILED->value,
|
||||
]);
|
||||
$this->execute_remote_command(
|
||||
[executeInDocker($this->deployment_uuid, "docker rm -f $this->container_name >/dev/null 2>&1"), "hidden" => true, "ignore_errors" => true],
|
||||
);
|
||||
|
|
|
|||
Loading…
Reference in a new issue