Guess no checklist or communication would work for team that ...frequently forget about sending new values from their local .env ove..., which you must have already done.
Your step in the pipeline should check for service availability before proceeding to next step, eg. does the service has endpoint registered within acceptable time, no endpoint means the backing pod(s) did not enter readiness state as expected. In such case, rollback and send notification to the team responsible for the service/application and exit cleanly.
There's no fix formula for CI/CD, especially human error. Check & balance at every step is the least you can do to trigger early warning and avoid a disastrous deployment.
发布评论
评论（1）
猜猜没有清单或通信对
...经常忘记从其本地.env ove ...发送新值的团队，您必须已经完成。您在管道中的一步应在继续下一步之前检查服务可用性，例如。该服务是否在可接受的时间内注册了端点，没有任何端点意味着衬托吊舱未按预期输入准备状态。在这种情况下，回滚并将通知发送给负责服务/申请的团队并干净地退出。
CI/CD没有修复公式，尤其是人为错误。检查＆amp;在每个步骤中，您至少可以做到触发预警并避免灾难性部署。
Guess no checklist or communication would work for team that
...frequently forget about sending new values from their local .env ove..., which you must have already done.Your step in the pipeline should check for service availability before proceeding to next step, eg. does the service has endpoint registered within acceptable time, no endpoint means the backing pod(s) did not enter readiness state as expected. In such case, rollback and send notification to the team responsible for the service/application and exit cleanly.
There's no fix formula for CI/CD, especially human error. Check & balance at every step is the least you can do to trigger early warning and avoid a disastrous deployment.