Validation: Deploy freezes for environments MVC

Problem Statement

It would be useful for gitlab.com full CD deployments to be able to specify windows of time when runners are paused for an environment or group of environments. This has the following use cases:

For a regularly scheduled cron like syntax:

• For teams that are not global, not as relevant to GitLab, the ability to halt CICD deployments off-hours.
• Suspend CICD pipelines on weekends when there is limited team availability.

For ad-hoc windows:

• Special events such as big announcements, livestreams, etc.
• Holidays where there is limited team availability.

Link to Opportunity Canvas

Reach

Release Managers and teams involved in executing releases

• The main difference between this and a pipeline implementer for a .gitlab-ci.yml is that the authors of these kinds of pipelines are much less technical, and even editing yaml might be a challenge (though they will still need to understand markdown.)
• Our internal customers are the #production team (for runbooks in general) and #delivery team (for release plans).

6.0 = Impacts a large percentage (~50% to ~80%) of the above

Impact

Like most other competitors in this space, they can orchestrate/facilitate blackout periods/moratoriums. 2.0 = High impact

Confidence

Others are solving this issue, in regulated industries this is common requirement and practice 80% = Medium confidence

Effort

TBD