Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
GitLab Community Edition
GitLab Community Edition
  • Project
    • Project
    • Details
    • Activity
    • Releases
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
    • Locked Files
  • Issues 14,073
    • Issues 14,073
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 800
    • Merge Requests 800
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Registry
    • Registry
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • GitLab.org
  • GitLab Community EditionGitLab Community Edition
  • Issues
  • #57430

Closed
Open
Opened Feb 07, 2019 by Brendan O'Leary 🐢@brendan🦊
  • Report abuse
  • New issue
Report abuse New issue

Group-level pipeline semaphores (follow up to project-level semaphores for pipelines)

When #20481 is implemented, it will be possible to limit pipeline execution based on semaphores at the project-level. This is a great feature, but given our extent of support for environments, pipeline variables, Kubernetes clusters, etc at the group level, after we implement semaphores at the project level, we should expand it to be able to be used at the group level.

/cc @jlenny @inorton

Related issues

Assignee
Assign to
Epic
FY20 Q4
Milestone
FY20 Q4
Assign milestone
Time tracking
None
Due date
No due date
7
Labels
Accepting merge requests Verify continuous delivery continuous integration devops:verify direction feature
Assign labels
  • View project labels
Reference: gitlab-org/gitlab-ce#57430