Skip to content

Include information about GitLab.com Runner machine types for a pool of shared runners

Release notes

Problem to solve

Runners at the project level (settings/ci-cd) do not indicate anything about Runner SaaS build machine compute types. Therefore, it is difficult for any user to figure out which types of Runners are available, the compute and memory resources available in that runner, how to use an identified Runner in their CI jobs, and the applied cost factor which impacts minutes used and their cost.

User story

As a GitLab SaaS CI user I want to quickly identify the available Runner machine types on GitLab SaaS for running my CI job.

JTBD

When I am troubleshooting CI jobs, I want to quickly know if the problem connects with the job execution agent, so I can resolve the problem and continue working.

Intended users

User experience goal

The user should be able to identify the machine type that their shared runners at their organization are using.

Proposal

TBD.

Must incorporate the following machine types:
Runner Type Shared Runner name Tags Run untagged jobs
Linux - Container Builds 1-green.shared.runners-manager.gitlab.com/default docker;east-c;gce;git-annex;linux;mongo;mysql;postgres;ruby;shared Yes
Linux - Container Builds 2-green.shared.runners-manager.gitlab.com/default docker;east-c;gce;git-annex;linux;mongo;mysql;postgres;ruby;shared Yes
Linux - Container Builds 3-green.shared.runners-manager.gitlab.com/default docker;east-c;gce;git-annex;linux;mongo;mysql;postgres;ruby;shared Yes
Linux - Container Builds 4-green.shared.runners-manager.gitlab.com/default docker;east-c;gce;git-annex;linux;mongo;mysql;postgres;ruby;shared Yes
Linux - Container Builds 5-green.shared.runners-manager.gitlab.com/default docker;east-c;gce;git-annex;linux;mongo;mysql;postgres;ruby;shared Yes
Linux - Container Builds 1-blue.shared.runners-manager.gitlab.com/default docker;east-c;gce;git-annex;linux;mongo;mysql;postgres;ruby;shared Yes
Linux - Container Builds 2-blue.shared.runners-manager.gitlab.com/default docker;east-c;gce;git-annex;linux;mongo;mysql;postgres;ruby;shared Yes
Linux - Container Builds 3-blue.shared.runners-manager.gitlab.com/default docker;east-c;gce;git-annex;linux;mongo;mysql;postgres;ruby;shared Yes
Linux - Container Builds 4-blue.shared.runners-manager.gitlab.com/default docker;east-c;gce;git-annex;linux;mongo;mysql;postgres;ruby;shared Yes
Linux - Container Builds 5-blue.shared.runners-manager.gitlab.com/default docker;east-c;gce;git-annex;linux;mongo;mysql;postgres;ruby;shared Yes
Windows - Shell Builds windows-shared-runners-manager-1 shared-windows;windows;windows-1809 No
Windows - Shell Builds windows-shared-runners-manager-2 shared-windows;windows;windows-1809 No
macOS - Shell Builds macOS shared runner (primary cluster) primary;shared-macos-amd64 No

Available Tier

  • Free

Links / references

AS-IS Workflow (Non-Empty Pipeline State)

Selecting_a_SaaS_Runner_User_workflow__v2

PM mockups

Mockups

--- --
1.Change navigation to Runners view runner_fleet
2.Catalog view shared_runners_catalog

This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.

Edited by 🤖 GitLab Bot 🤖