Permissions-based approval system

[kitallis]

Proposal

a.k.a sign-offs.

Certain users or a group of users have the authority to stop a release train from moving ahead. They can reject builds as faulty or completely halt the release from happening.

These users may typically be QAs (in a large team) on a more continuous basis or they could be business stakeholders involved in engineering on a less frequent basis.

What this achieves / problem(s) it solves

The assigned users might be able to:

• Stop the release team from deploying to any further channels
• Stop the release team from create new releases
• Approving or reject certain fixes to a release
• Having the final say in the release to a production store

Additionally,

• Be able to submit a reason (review notes) for acceptance or rejection per build or per release
• Be able to tentatively approve with review notes, even if the release is not 100% golden

This system is similar to the GitHub / GitLab PR approval system

Additional context

The users who are selected for this approval system should ideally only be of a certain role or permission.

We have previously built a simple sign-offs system that is now defunct.