Skip to content

Local trigger `app‐deploy [optional trigger]`

Jasmin Abou Aldan edited this page Jan 14, 2025 · 1 revision

Script should be run just by calling the script name from the folder where .deploy-options.sh is stored (e.g. root folder):

app-deploy

After that, the script will check if everything is pushed to the remote, and if needed it will push all commits before it continues (automatic push can be enabled with enable_automatic_commit_push flag).

###############################################################
#                         DEPLOY SCRIPT                       #
#                                                             #
#                   Copyright (c) 2020 Infinum.               #
###############################################################


###############################################################
#                      COMMIT CHECK                           #
###############################################################

---------------------------------------------------------------
Targeting commit: e3e45889b
---------------------------------------------------------------
#123: Add my cool feature
---------------------------------------------------------------

The next step is selecting one or multiple targets that should be run on CI. Enter one or more numbers separated by whitespaces:

###############################################################
#                  DEPLOY TARGET SELECTION                    #
###############################################################

--------------
| TryOutApps |
--------------

[0] Test
[1] Develop
[2] Production

==================

---------
| STORE |
---------

[3] App Store

Enter number in square brackets: 0 1

After selecting the target, the script will ask for the changelog. The console will open a preselected text editor where a changelog can be added. Keep in mind that closing that editor without entering the changelog will result in a script termination.

###############################################################
#                          CHANGELOG                          #
###############################################################

------------------------------------------------------------
Enter changelog message...
------------------------------------------------------------

If everything is done correctly, the confirmation step will be shown with the summary of selected options (can be skipped by disabling the enable_final_confirmation flag):

###############################################################
#                          DEPLOY                             #
###############################################################

---------------------------------------------------------------
                      ~ CONFIGURATION ~

Tag: ci/internal-develop/internal-test/2024-12-16T10-26

Changelog:
New features:

* first
* second
---------------------------------------------------------------

Is configuration correct for the CI deployment? [y or enter / n]

In the end, the tag is created and pushed to the remote.

Clone this wiki locally