Skip to content

Establish separate categories for Runner SaaS, Runner Core, and Runner Fleet

Darren Eastman requested to merge runner-direction-update-2021_09_22 into master

As of this time, we have not evaluated the maturity of Runner and its sub-categories taking into account recently refined jobs to be done (JTBD). This merge request proposes to decompose Runner into distinct categories for Runner SaaS, Runner Core, and Runner Fleet.

Today, we group all the analyst use cases for build agents under Runner. Although, both Forrester and Gartner consider SaaS CI in a different solution as evidenced by cloud-native CI report. Creating a separation between Runner core and cloud allows us to more transparently defend our position as a CI leader in the market. Runner Fleet enables the modern technology operations for organizations which is a key need for change management of DevOps.

By splitting Runner into separate categories we are able to assign different metrics, competitive landscapes, and independently assign maturity to each category. This will transparently convey to the internal stakeholders the priorities and trade offs the team is making in the Runner portfolio.

Approvals

Merge requests with changes to stages and groups and significant changes to categories need to be created, approved, and/or merged by each of the below:

  • Chief Product Officer @sfwgitlab
  • VP of Product @adawar
  • The Product Director relevant to the stage group(s)
  • The Engineering Director relevant to the stage group(s)
  • Director of Product Design @vkarnes
  • CEO

The following people need to be on the merge request so they stay informed:

  • Chief Technology Officer @edjdev
  • Vice President of Development @clefelhocz1
  • Vice President of Quality @meks
  • Vice President of User Experience @clenneville
  • The Product Marketing Manager relevant to the stage group(s)
  • Senior Manager, Technical Writing @susantacker
Edited by Mek Stittri

Merge request reports