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

Improving and optimizing our fastlane workflow


Let's put our theory into practice and improve our Fastfile by including purposeful Git actions, starting with a lane that you may have noticed previously, but that we haven't covered yet, namely the prebuilt before_all * lane. This lane gets called before any fastlane lane is called, and is a great place to put any actions and commands that would commonly apply across all of the lanes—for instance, when running any preparation or cleanup scripts prior to calling a build or test.

Working with the before_all lane

We are going to start off by calling the carthage (https://docs.fastlane.tools/actions/carthage/#carthage) action to ensure we have the most up-to-date dependencies. Using the bootstrap command argument, we can optimize this call so that it only downloads the necessary dependencies as required:

platform :ios do
  before_all do
    carthage(
      command: options[:update] ? "update" : "bootstrap",
      platform: "iOS",
      use_binaries...