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,331
    • Merge requests 1,331
  • 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
  • #37366
Closed
Open
Issue created Nov 26, 2019 by Juan J. Ramirez@jj-ramirez👁Contributor

View and Manage an Organization's Runners at the Group Level

Problem to solve

A large GitLab enterprise customer that is migrating from GitHost to GitLab.com needs to be able to (1) view and manage all jobs and (2) view and manage all Runners for their organization.

Currently, in GitLab.com, there's no way to manage Runners settings at the Group Level. This is required for customers who are migrating from the self-hosted version and want to control their specific and shared runners based on projects.

Value/benefit to customer

“This capability is available within the Admin Area of self-hosted Gitlab and is extremely useful when working with teams, assisting them with configuration/troubleshooting of Runners/Pipelines as it gives us a centralized place to view/manage those resources. In Gitlab.com, in order to help users with the same, we need to gain access at the subgroup/project level to their resources just to begin assisting/troubleshooting.

Intended users

  • Delaney (Development Team Lead)
  • Sasha (Software Developer)
  • Devon (DevOps Engineer)

Proposal

  • Enable the same Runner management view available at the Admin level in EE, so it can be accessed from the Group level in GitLab.com.

  • Expose a similar view as is available in the GitLab.com admin area where the customer/user can is able to view Runners at the organization level.

  • In this view, the user should be able to edit, pause, stop a Runner.

  • Allow specific users to control high-level Runner settings at the Group level.

Permissions and Security

This view will only be available for Group Owners.

Not doing

May 18 2020: The ability to display group level jobs will need to be considered for delivery in a separate issue as the current layout in development results in a database query that does not meet GitLab's database query performance benchmarks.

Edited Jul 09, 2020 by Darren Eastman
Assignee
Assign to
Time tracking