Book Image

Continuous Delivery for Mobile with fastlane

By : Doron Katz
Book Image

Continuous Delivery for Mobile with fastlane

By: Doron Katz

Overview of this book

Competitive mobile apps depend strongly on the development team’s ability to deliver successful releases, consistently and often. Although continuous integration took a more mainstream priority among the development industry, companies are starting to realize the importance of continuity beyond integration and testing. This book starts off with a brief introduction to fastlane—a robust command-line tool that enables iOS and Android developers to automate their releasing workflow. The book then explores and guides you through all of its features and utilities; it provides the reader a comprehensive understanding of the tool and how to implement them. Themes include setting up and managing your certificates and provisioning and push notification profiles; automating the creation of apps and managing the app metadata on iTunes Connect and the Apple Developer Portal; and building, distributing and publishing your apps to the App Store. You will also learn how to automate the generation of localized screenshots and mesh your continuous delivery workflow into a continuous integration workflow for a more robust setup. By the end of the book, you will gain substantial knowledge on delivering bug free, developer-independent, and stable application release cycle.
Table of Contents (27 chapters)
Title Page
Dedication
www.PacktPub.com
Foreword
Contributors
Preface
Index

Collective code signing


Previously this book has discussed how we would automate and manage the process of creating certificates and provisioning profiles, and subsequently, code signing through public/private keys (separately, for both development and distribution). We discussed the theory and processes for working with profiles and certificates in great detail, and while fastlane has done a great job in allowing developers to not only manage but also repair their code signing assets with sigh and cert, there is one glaring problem—each developer still has an individual profile, and that leads to numerous profiles.

The number of profiles will grow as the teams grow, and, even with personnel leaving, they have to be pruned over time; needless to say, it's a model that isn't exactly scalable. Each new machine will require quite a bit of setting up using individual code signing credentials, with new provisioning profiles having to be set up each time a new device is added or removed, or in...