• How We Release the Spotify App: A Look Under the Hood (Part 2) Introduction In Part 1 of “How We Release the Spotify App”, we gave an overview of how the Spotify release process works. • In Part 2, we will peek under the hood at the tooling that makes it possible. • To understand where we are today, it’s useful to give some historical context of how the current solution came to be. • Back in the Dark Age before the Release Manager Dashboard, everything lived in Jira. • And we mean everything. • While Jira is powerful (sometimes overwhelmingly so), it struggles to present lots of information in a human-friendly way.
Article Summaries:
- Spotify has unveiled the second part of its “How We Release the Spotify App” series, detailing the tooling behind its release process. The company introduced the Release Manager Dashboard, a single web page that consolidates data previously scattered across Jira tickets. Designed to reduce context‑switching for release managers, the dashboard displays track‑specific information-release state, blocking bugs, sign‑off status, build verification, and quality metrics such as crashes and CPU exceptions. It also highlights unassigned bugs that could impede releases. By centralizing this data, Spotify aims to streamline decision‑making and improve the efficiency of its Android, iOS, and desktop release workflows.
Sources: