Skip to content

Latest commit

 

History

History
 
 

Touchwonders

Folders and files

NameName
Last commit message
Last commit date

parent directory

..

actions

actions

 
 

Fastfile

Fastfile

 
 

README.md

README.md

 
 

fastlane_config.yaml

fastlane_config.yaml

 
 

README.md

fastlane documentation

Installation

sudo gem install fastlane

Architecture

Remote Fastfile

In Touchwodners we decided to implement a base collection of standard lanes and actions that we want to share among all our projects. To import them we take advantage of import_from_git action.

At very beginning of every project's Fastfile:

import_from_git(url:"{touchwonders_git_repo}:/library/fastlane.git", path:"Fastfile")

Configuration file

Every project's fastlane folder contains a required configuration file responsible to load proper environment and settings per project deployment.

Example: fastlane_config.yaml

Available actions

iOS

Load release notes

Load release notes for current project's deployment.

Every project root folder contains:

  • build_notes.md: Markdown file containing the release note of latest deployed version. For project management reasons this file is kept under version control.
  • RELEASE_NOTES.md: Markdown file contaning a collection of all the build notes that have been deployed. For project management reasons this file is kept under version control.

At every interaction the build note file content is added to RELEASE_NOTES.md collection and finally used for fill in Crashlytics build's release notes.

GIT Checkout

Checkout a branch from project working copy.

Availabe lanes

The predefined lanes are divided in public and private.

The rule of thumb is to keep the public lanes as simple as possible by leveraging all the implementation load to private lanes such that they can be easily re-used.

Public lanes

Development

Description: Submit a new daily build to Crashlytics.

Steps:

  • Increment build number
  • Download latest provisioning profile for targets specified in fastlane_configuration.yaml file.
  • Add icon overlay if needed (see fastlane_configuration.yml)
  • Publish to Crashlytics. By default all Touchwonders team is invited.

Stable

Description: Submit a new sprint-end/weekly build to Crashlytics.

Steps:

  • Increment build number
  • Download latest provisioning profile for targets specified in fastlane_configuration.yaml file.
  • Add icon overlay if needed (see fastlane_configuration.yaml)
  • Publish to Crashlytics. By default all Touchwonders team is invited.

Release

Description: Submit a new app version to AppStore.

Steps:

  • Download latest provisioning profile for targets specified in fastlane_configuration.yaml file.
  • Upload to iTunes Connect.

Private lanes

config_env

Description: Configure the environment to drive required lanes with provided options.

Steps:

  • Select proper Xcode tool by looking up the xcode_select parameter defined in project’s fastlane_configuration.yaml file.

prepare

Description: Prepare required tools to drive required lanes with provided options.

Step:

  • Ensure clean git status.
  • Checkout/Pull latest and greatest from remote_branch parameter specified in project’s fastlane_configuration.yaml file.
  • Cocoapods.

get_provisioning_profile

Description: Create/Renew/Download required provisioning profiles for all targets specified in fastlane_configuration.yaml file.

Step:

  • Download targets provisioning profile. Every targets provides an identifier which is used to create an environment variable containing proper mobile provisioning profile UDID. This is useful in case the UDID is fetched from an environment variable, in your Xcode project’s setting.

project_warm_up

Description: Last step before ‘build&archive’ process.

Step:

  • Add icon overlay if needed.
  • Increment build number. N.B.: Release lane will never increment project build number.

build_and_archive

Description: Build and export IPA for your project. All intermediate and final step result are named after project’s scheme defined in the fastlane_configuration.yaml

Step:

  • Build project by using parameters specified in fastlane_configuration.yaml file.
  • Export build’s product to IPA.

publish

Description: Publish build to Crashlytics by using build notes available in build_notes.md file.

Step:

  • Load build release notes from build_notes.md file and updated RELEASE_NOTES.md changelog.
  • Publish build to Crashlytics. When specified, emails have prevalence over groups notification.

More information about fastlane can be found on https://fastlane.tools. The documentation of fastlane can be found on GitHub