Building a resilient CI/CD pipeline at scale is no easy feat, especially when working with a rapidly evolving business like Zomato. In this talk, we will discuss how we reimagined our CI/CD process by leveraging GitHub Actions and creating a robust system for safe and fast deployments. We will cover
Why GitHub Actions stood out as the ideal choice, how we orchestrated scalable and ephemeral runners using AWS ECS with auto-scaling, ensuring security, isolation, and optimized resource usage without hindering user experience.
How we transitioned our CI/CD to this new orchestration integrating features to enrich the experience such as caching packages, canary deployments, real-time monitoring, auto-abort and rollback mechanisms, etc.
Beyond infrastructure, we will also cover the standards we follow for rolling out changes across different environments.
This talk will offer actionable insights into building a CI/CD pipeline that's not just fast and efficient but also intuitive and secure.
This talk provides a clear blueprint for standardizing CI/CD at scale, integrating advanced automation, and building resilient systems that are developer-friendly.
For engineers and operators, it showcases:
How to manage CI/CD infrastructure efficiently with Github Actions.
How to automate, standardize, and enforce linters across repositories.
How to build a complete deployment cycle with all the safeguards, proper visibility, and approval workflows.
Advanced automation features that enhance reliability during deployments while reducing human intervention.
The talk also sheds light on the role of GitHub Actions as a unified platform for CI/CD, emphasizing how it streamlines workflows, enhances developer experience, and reduces the need for multiple tools or systems. By sharing Zomato’s journey, this talk aims to inspire practitioners to rethink and enhance their own CI/CD setups, making them more resilient and developer-focused.
I'm marking this as a reject because the talk doesn't fit the track it was submitted under at all (Open Data Devroom).
Perhaps this was meant for a different track? Will remove my review once it is slotted correctly.