Do not retry review-deploy under any circumstances
What does this MR do and why?
Revert of !114444 (merged).
The initial hope was that retrying the job would solve issues happening in https://gitlab.com/gitlab-org/quality/engineering-productivity-infrastructure/-/issues/53 or https://gitlab.com/gitlab-org/quality/engineering-productivity-infrastructure/-/issues/60, but sadly, practice shows that it doesn't. Those problems are happening in the three job retries.
Additionally, retrying the job and not the entire review-app pipelines create issues with the helm release: see #404583 (comment 1356790879).
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Edited by David Dieulivol