Skip to content

Script modifications

Jump to bottom
Jonatan Pleško edited this page Feb 11, 2025 · 2 revisions

Main option app-deploy init

Once deploy-options are generated with the init command, the script should be used as-is.

The only part that should be changed is stored inside the .deploy-options.sh file under the deploy_options function. This part of the script is responsible for creating the first part of the tag that can trigger a specific workflow on CI. If the given values are not enough or do not represent the project structure, they can be replaced with different values.

Keep in mind that the prefix internal-' should be used for builds created for internal testing, while builds for beta testing (e.g., Google Play Beta or Apple TestFlight) or public release should be prefixed as beta—' or play store/ app store.

Final variable name inside the deploy_options function must stay: environments

Configuration flags

As tag creation is divided into several small steps, some can be skipped and/or disabled by changing configuration flags at the beginning of the script inside the .deploy-options.sh file.

# If enabled, the console will be cleared on every script run.
# By default, this option is enabled
use_automatic_console_clean=true
# If enabled, commits that are not pushed will be pushed automatically without a confirmation dialog.
# By default, this option is disabled
enable_automatic_commit_push=false
# If enabled, a confirmation dialog with a deploy summary will be presented.
# By default, this option is enabled
enable_final_confirmation=true

Script version

If needed, you can specify the version of the script you want to run by changing the value of the script_version parameter. Available options are v1 for the old (legacy) deployment flow and v2 for the new deployment flow. v1 Old deployment flow where local app-deploy command will generate a tag that includes and defines the app version and following build number without the ci/ prefix (e.g.,. internal-staging/v1.0.0-200).

v2 This is a new deployment flow in which the local app-deploy command generates the new trigger tag described at the beginning of this readme.

Clone this wiki locally