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

Updating our Fastfile


Open up the Fastfile we worked on in the previous chapter and go to the beta lane. We are simply going to add one line below the other commands, so your lane should now look something like this:

  lane :beta do
    register_devices(devices_file: "devices.txt")
    match(git_url: "[email protected]:doron_katz/my-fastlane-keys.git",
      type: "development",
      app_identifier: "com.doronkatz.firefox")
      pem
  end

Our lane is starting to look more comprehensive by the day. Let's run the entire lane again by typing the following in the Terminal:

fastlane beta

The output should produce something similar to the following:

[20:59:44]: -------------------------------------------------
[20:59:44]: --- Step: Verifying required fastlane version ---
[20:59:44]: -------------------------------------------------
[20:59:44]: Your fastlane version 2.46.1 matches the minimum requirement of 2.41.0  
[20:59:44]: ------------------------------ [20:59:44]: --- Step: default_platform...