Skip to content
GitLab
Next
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • GitLab GitLab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 44,761
    • Issues 44,761
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1,329
    • Merge requests 1,329
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.orgGitLab.org
  • GitLabGitLab
  • Issues
  • #352316
Closed
Open
Issue created Feb 08, 2022 by Dennis Tang@dennis🚀Developer

Move required pipeline configuration to Ultimate

Overview

The required pipeline configuration feature is deprecated in GitLab 14.8 for Premium customers and is scheduled for removal in GitLab 15.0. This feature is not deprecated for GitLab Ultimate customers.

Proposal

  • The required pipeline configuration feature will be moved to the Ultimate tier by default
  • GitLab will preserve a way via feature flag or another similar capability of enabling this for individual Premium customers as needed (see requirement from @ogolowinski)

Rationale

This change to move the feature to GitLab's Ultimate tier is intended to help our features better align with our pricing philosophy as we see demand for this feature originating primarily from Executives. This change will also help GitLab remain consistent in its tiering strategy with the other related Ultimate-tier features of security policies and compliance framework pipelines.

Edited Apr 07, 2022 by Sam Kerr
Assignee
Assign to
Time tracking