Subject
Platform migration: sunsetting Jenkins in favor of GitHub Actions across all product engineering teams
After an eighteen-month evaluation led by the Platform Infrastructure group, we will be retiring our self-hosted Jenkins cluster and consolidating all continuous integration and delivery pipelines onto GitHub Actions. The transition begins November 4 and concludes February 28, 2025.
Our Jenkins deployment has grown to 412 pipelines across 8 controllers, with an average job-queue wait of 7.3 minutes and a plugin surface that has become operationally expensive to maintain. GitHub Actions gives us native integration with our source of truth, reusable workflows, hosted runners with autoscaling, and a measurable 38% reduction in median build time from the pilot cohort. It also eliminates the on-call burden that Platform has absorbed for the past three years.
NOV 04 — NOV 22
Phase I · Foundation & Reusable Workflows
Platform team publishes the internal action catalog, reusable workflows, and organization-level secrets. Runner pools provisioned in us-east-1 and eu-west-1.
In Motion
DEC 02 — DEC 20
Phase II · Tier-3 services (non-critical)
Internal tooling, documentation pipelines, and back-office services migrate first. Expect roughly 140 repositories in scope for this phase.
Queued
JAN 06 — JAN 31
Phase III · Tier-2 services
Customer-facing applications, data pipelines, and mobile build chains. Each team owns its cutover with Platform pairing available on request.
Queued
FEB 03 — FEB 28
Phase IV · Tier-1 & Jenkins shutdown
Billing, identity, and payments pipelines migrate under full change-management review. Jenkins controllers enter read-only on Feb 24 and are decommissioned Feb 28.
Planning
!
No new Jenkins pipelines should be authored after November 1. If your team has a pipeline in active development, contact Platform before the end of this week so we can redirect the work onto the new foundation and avoid rework.
Three live sessions, each recorded and posted to the Engineering Wiki within 24 hours. Registration links are in the #migration-ga Slack channel.
TUE · OCT 29 · 10:00 PT
Authoring Workflows — Fundamentals
THU · NOV 07 · 13:00 PT
Reusable Workflows & the Action Catalog
WED · NOV 20 · 11:00 PT
Secrets, Runners & Compliance
04
Team leads & accountability
DO
Daniel Okafor
Principal Engineer, Platform Infrastructure
Program lead · foundation
MA
Mireille Asante
Staff Engineer, Developer Experience
Reusable workflows · catalog
JV
Jure Vuković
SRE Lead, Production Systems
Runners · secrets · compliance
SH
Saoirse Hensley
Engineering Manager, Payments
Tier-1 cutover owner
RK
Rohan Kapadia
Engineering Manager, Data Platform
Pipelines · airflow bridges
EB
Elena Brasov
Staff Engineer, Mobile
iOS & Android build chains
05
What I am asking of you
Each engineering manager will receive a per-team migration tracker by Friday, October 18. Please review it with your team during your next planning session, nominate a migration champion, and confirm your Phase window with Daniel Okafor no later than October 25. Treat this as planned work — it should appear on your roadmap, not in the margins of it.
I know shifting CI systems is never glamorous work, but the teams who piloted this change have told us the developer experience afterward is meaningfully better. I am grateful for the care you will bring to it, and especially to the Platform group who have been preparing the ground for months.
Priya Ramanathan
Vice President, Engineering · Helix Systems
cc: CTO · CISO
slack: #migration-ga
wiki: eng/ci-migration