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

Summary


In the preceding chapters, we learned about the various aspects of fastlane that help us with our continuous delivery workflow. This chapter was all about communicating the various actions to stakeholders via the popular developer communication platform Slack. We learned how to configure Slack to give us a webhook URL so that we can call the slack action within our various lanes.

Ideally, we should look at leveraging Slack for all the critical lane conclusions in our workflow, from successful or failed tests to internal distributions, publishing to the App Store, and even in conjunction with Git-specific actions, such as triggering a Git pull request.

In our final chapter, we take a holistic look at best practices with fastlane to further fine-tune our continuous delivery goals.