Gitlab hero border pattern left svg Gitlab hero border pattern right svg

Category Direction - Runner Fleet

Runner Fleet

Our vision is to provide users with a birds-eye view, configuration management capabilities, and predictive analytics to administer a fleet of GitLab Runners easily. This category's north star delivers an industry-leading user experience as measured by system usablity scores and the lowest maintenance overhead for customers who self-manage a CI build platform at scale.

Who we are focusing on?

Check out our Ops Section Direction "Who's is it for?" for an in depth look at the our target personas across Ops. For Runner, our "What's Next & Why" are targeting the following personas, as ranked by priority for support:

  1. Priyanka - Platform Engineer
  2. Devon - DevOps Engineer
  3. Sasha - Software Developer
  4. Delaney - Development Team Lead

Strategic Priorities

The table below represents the current strategic priorities for Runner Fleet. This list will change with each monthly revision of this direction page.

Item Why? Target delivery QTR  
Runner Fleet Foundations The foundational capabilities are the building blocks required to deliver an improved experience for managing runners at scale. FY22 Q4  
Runner Admin View Usability Improvements The 2021 Q3 UX scorecard of the current runner administrative user experience identified several areas that needed improvement regarding workflow and user experience. In conjunction with the foundations' work effort, the usability improvements enable future iterations that will include new features and capabilities. FY23 Q1  
Runner Search, Association and Data Export for Admin and Group views Including an assigned group or project data element and adding the ability to export the runner data from GitLab will significantly simplify the operational overhead of locating and troubleshooting runners across an enterprise installation of GitLab. FY23Q1  
Runner Group View Usability Improvements The usability improvements described above for the admin view are relevant to the group view. For customers on GitLab SaaS, they use this interface to manage and administer runners that they self-host. Therefore, any usability and feature improvements in the Admin view must also be made available in the Group view. FY23 Q1  
Runner Admin View New Features With the foundations in place, we will now be able to deliver new features more quickly. These include summary metrics on all runners associated at the instance, group, or project levels, improved search and filtering, runner association to a project or group, automated removal of stale runners. FY23 Q2  
Runner Group View New Features With the foundations in place, we will now be able to deliver new features more quickly. These include improved search and filtering, runner association to a project or group, automated removal of stale runners. FY23 Q2  

Maturity Plan

Give Feedback

The near features highlighted here represent just a subset of the features and capabilities that have been requested by the community and customers. If you have questions about a specific runner feature request or have a requirement that's not yet in our backlog, you can provide feedback or open an issue in the GitLab Runner repository.

Revision Date

This direction page was revised on: 2022-01-10

Git is a trademark of Software Freedom Conservancy and our use of 'GitLab' is under license