On the jump server the CLI-suite is installed. It initiates the rollout by notifying the configuration management system that this application deployment is to be initiated. The current source code is loaded from the specified sources and stored on a distributed file system for further processing.

Starting the deployment of several roles at the same time (“parallel deployments”) is only possible under these conditions:

• Roles for parallel deployment must not be on the same instances.

• You must run the deployment in two stages:

  • Stage 1: Update the sources sequentially in one ssh session (parameter -m): r3 deploy -mr role1; r3 deploy -mr role2

  • Stage 2: Deploy the source code to the target instances (parameter -n) in separate ssh sessions for each role:

    1. SSH-Session 1: r3 deploy -nr role1

    2. SSH-Session 2: r3 deploy -nr role2

~$ r3 deploy -h

# Response
Deploy software to instances in project environment

optional arguments
usage: r3 deploy [-h,] [--helpr ROLE] [--init-hook [INITHOOKDIR]] [--pre-hook [PREHOOKDIR]] [--post-hook [POSTHOOKDIR]] [--rev REV] [-n]  show this help message and exit
  -d                    run in debug mode
  -q       [-m] [--sanity-check] [--list-roles | --list-sources] [-d] [-q]

optional arguments:
  -h, --help            show runthis inhelp quietmessage modeand (onlyexit
errors are shown)
  -pr PROJECTROLE, --projectrole PROJECTROLE  Server role to work on
  --init-hook [INITHOOKDIR]
               The necessary name of the project to work on Run initial -rhook ROLE, --role ROLE  Server role to work onscripts in default path "init-hook.d/" or given directory (optional)
  --pre-hook [PRE_HOOKPREHOOKDIR]
                        runRun pre-deploy hook scripts in default path "pre-
                        hook.d/" or given directory (optional)
  --post-hook [POST_HOOKPOSTHOOKDIR]
                        runRun post-deploy hook scripts in default path "post-
                        hook.d/" or given directory (optional)
  --rev REV             specifySpecify tag/branch/revision to clone (git deployment only!)
  -n, --skip-update     Skip update of source code (optional)
  -m, --skip-deploy     Skip distribution of source code only!(optional)
  --listsanity-rolescheck        only check listthe deployablesanity rolesof andall exitcomponents
  --list-sourcesroles          listList sourcedeployable detailsroles and exit
  --list-nsources        List source details and exit
  -d, --debug    skip update of source code (optional)  Run -min debug mode.
  -q, --quiet           Run in quiet skipmode distribution(only oferrors source code (optional)are shown).

~$ r3 deploy --list-roles

# Response
+-------+
| Roles |
+-------+
| admin |
+-------+
| api   |
+-------+
| web   |
+-------+

~$ r3 deploy --role YOUR-ROLE 

~$:r3 [instance] deploy --list-sources [--role ROLE]

# Response
+-------+-------------------+-------------------------------------------------------------+--------+----------+
| Roles | Deployment Method | Source                                                      | Branch | Excludes |
+-------+-------------------+-------------------------------------------------------------+--------+----------+
| web   | git               | ssh://gogs@git.root360.de:2222/3rd-party/simple-php-app.git | master | None     |
+-------+-------------------+-------------------------------------------------------------+--------+----------+

 2016-01-25 22: 34: 16,087 - deploy.py - INFO - Starting Deploying for role "web" in project "xxxxxxxx"
 2016-01-25 22: 34: 16,088 - deploy.py - INFO - Checking out project.
 ************
 2016-01-25 22: 34: 28.957 - deploy.py - INFO - SourcesTests updated
 2016-01-25 22: 34: 29.958 - deploy.py - INFO - Calculating the number of deployed targets.
 2016-01-25 22: 34: 31.891 - deploy.py - INFO - Deploying for 2 target (s).
 2016-01-25 22: 34: 31.892 - deploy.py - INFO - total: 2, success: 0, fail: 0
 ************************************************** **********
 ****************************
 2016-01-25 22: 39: 00.596 - deploy.py - INFO - total: 2, success: 1, fail: 0
 ****************************
 2016-01-25 22: 39: 28.673 - deploy.py - INFO - total: 2, success: 2, fail: 0
 2016-01-25 22: 39: 28,673 - deploy.py - INFO - Deploy finished without errors 

r3 deploy ...;  echo $?