Team
See the SaaS Platforms Organizational Structure for teams in Infrastructure.
Distinguished Engineer, Infrastructure - Andrew Newdigate
GitLab Dedicated Group
Mission
The GitLab Dedicated team’s mission is to create a fully managed, single-tenant GitLab environment, served through a GitLab Dedicated platform. It is developed to remove any manual interactions with customer tenant installations, and to ensure that the customer tenants are fully focused on unlocking the power of The One DevOps Platform.
Vision
The GitLab Dedicated group is a customer facing team, with team members focused on a high level of infrastructure automation, and enabling customer interactions with the GitLab Dedicated platform.
Production Engineering Foundations Team
Mission
The mission of the Production Engineering Foundations team at GitLab is to own the lifecycle of the core infrastructure for GitLab Saas instances and services. We seek to reduce the effort required to provide our core infrastructure services, and to enable other teams to self-serve core infrastructure that allows them to more efficiently and effectively run their services across all GitLab offerings.
Vision
The Foundations teams North Star consists of two pieces:
Production Engineering Ops Team
Mission
The Ops team is an infrastructure team under SaaS Platforms that focuses on improving processes that are vital to the succesfull operations of GitLab.
Vision
The Ops teams vision is to enable service onwers to operate their own services using standardized processes, frameworks, architectures and tools. Some of those processes and tools will be built by the Ops team, but many will be from other Infrastructure teams.
Runway Team
Mission
The Runway team builds and supports the Runway product, which aims to enable teams to deploy their code to staging & production quickly, safely and efficiently.
Ownership
The team has ownership over the following areas:
Services
The Runway team handles issues labeled Service::Runway
For services deployed to Runway, the Runway team is responsible for building functionality for the platform, operating the platform, and maintaining the platform for service owners.
Scalability Group
Common Links
Workflow | Team workflow |
GitLab.com | @gitlab-org/scalability |
Issue Trackers | Scalability |
Team Slack Channels | #g_scalability - Company facing channel #g_scalability-observability - Team channel #g_scalability-practices - Team channel #scalability_social - Group social channel |
Information Slack Channels | #infrastructure-lounge (Infrastructure Group Channel), #incident-management (Incident Management), #alerts-general (SLO alerting), #mech_symp_alerts (Mechanical Sympathy Alerts) |
Project Management Links
Group Level
- Scalability Epic Board
- Scalability Issue Board
- Scalability Issues not in an Epic
- Scalability Issues by Team
- Scalability Issues by Team Member
Teams
The Scalability group is currently formed of two teams:
46417d02
)