|Workflow||How may we be of service?||GitLab.com Status|| |
|Issue Trackers||Infrastructure: Milestones, OnCall||Production: Incidents, Changes, Deltas||Delivery|
|Slack Channels||#sre-lounge, #database||#alerts, #production||#g_delivery|
|Operations||Runbooks (please contribute!)||On-call: Handover Document, Reports|
The Delivery Team enables GitLab Engineering to deliver features in a safe, scalable and efficient fashion to both GitLab.com and self-managed customers. The team ensures that GitLab's monthly, security, and patch releases are deployed to GitLab.com and publicly released in a timely fashion.
By its own nature, the Delivery team is a backstage, non-user feature facing team whose product and output has a direct impact on Infrastructure's primary goals of availability, reliability, performance, and scalability of all of GitLab's user-facing services as well as self-managed customers. The team creates the workflows, frameworks, architecture and automation for Engineering teams to see their work reach production effectively and efficiently.
The Delivery team is focused on our CI/CD blueprint by driving the necessary changes in our software development processes and workflows, as well as infrastructure changes, to embrace the benefits of CI/CD.
Each member of the Delivery team is part of this vision:
The following people are members of the Delivery Team:
|Marin Jankovski||Engineering Manager, Delivery|
|Robert Speicher||Senior Backend Engineer, Delivery|
|Yorick Peterse||Staff Backend Engineer, Delivery|
|John 'Jarv' Jarvis||Senior Site Reliability Engineer, Delivery|
|Alessio Caiazza||Senior Backend Engineer, Infrastructure|
|John T Skarbek||Senior Site Reliability Engineer, Delivery|
The following members of other functional teams are our stable counterparts:
|Filipa Lacerda||Senior Frontend Engineer, Release (CD), Verify (CI) & Delivery|
Every Delivery team member is responsible for creating a training session for the rest of the team. See the page on team training for details.