set_build_number_repository

Set the build number from the current repository

This action will set the build number according to what the SCM HEAD reports.
Currently supported SCMs are svn (uses root revision), git-svn (uses svn revision) and git (uses short hash) and mercurial (uses short hash or revision number).
There is an option, :use_hg_revision_number, which allows to use mercurial revision number instead of hash.

set_build_number_repository
Supported platforms ios, mac
Author @pbrooks, @armadsen, @AndrewSB

2 Examples

set_build_number_repository
set_build_number_repository(
  xcodeproj: "./path/to/MyApp.xcodeproj"
)

Parameters

Key Description Default
use_hg_revision_number Use hg revision number instead of hash (ignored for non-hg repos) false
xcodeproj explicitly specify which xcodeproj to use

* = default value is dependent on the user's system


Documentation

To show the documentation in your terminal, run

fastlane action set_build_number_repository

CLI

It is recommended to add the above action into your Fastfile, however sometimes you might want to run one-offs. To do so, you can run the following command from your terminal

fastlane run set_build_number_repository

To pass parameters, make use of the : symbol, for example

fastlane run set_build_number_repository parameter1:"value1" parameter2:"value2"

It's important to note that the CLI supports primative types like integers, floats, booleans, and strings. Arrays can be passed as a comma delimited string (e.g. param:"1,2,3"). Hashes are not currently supported.

It is recommended to add all fastlane actions you use to your Fastfile.


Source code

This action, just like the rest of fastlane, is fully open source, view the source code on GitHub


Back to actions