Chapter 9. OpenShift Build Process

Build Phase

1. Runs the gear stop command to stop the application.
2. Runs the control pre-receive command on the primary cartridge.
3. Runs the control pre-repo-archive command on the primary cartridge.
4. Creates a new application directory: $OPENSHIFT_HOMEDIR/app-deployments/$date_$time and dependent subdirectories.

   Note

   If your cartridge requires a particular directory structure for dependencies, create a symbolic link for your cartridge directory structure into $OPENSHIFT_DEPENDENCIES_DIR. Use $OPENSHIFT_BUILD_DEPENDENCIES_DIR for build time only dependencies.
5. Copies $OPENSHIFT_HOMEDIR/app-root/runtime/dependencies from the active application to $OPENSHIFT_HOMEDIR/app-deployments/$date_$time/dependencies.
6. Removes previous applications starting from the oldest until the number set at $OPENSHIFT_KEEP_DEPLOYMENTS is reached.
7. Copies the new application source code to $OPENSHIFT_REPO_DIR. This is the only point in the build life cycle when OpenShift Enterprise copies the application source code.
8. Runs the control pre-build command on the primary cartridge.
9. Runs the pre-build user action hook, if present.
10. Runs the control build command on the primary cartridge.
11. Runs the build user action hook, if present.

Preparation Phase

1. OpenShift Enterprise runs the prepare user action hook, if present.
2. The application ID and checksum of application contents are calculated.
3. OpenShift Enterprise creates $OPENSHIFT_HOMEDIR/app-deployments/by-id/$deployment_id and points to ../app-deployments/$date_time

Distribute Phase

1. OpenShift Enterprise synchronizes the new application with all child gears if the application is scalable.

Deploy Phase

1. Updates $OPENSHIFT_HOMEDIR/app-root/runtime/repo so it points to ../../app-deployments/$date_$time/repo
2. Updates $OPENSHIFT_HOMEDIR/app-root/runtime/dependencies so it points to ../../app-deployments/$date_$time/dependencies
3. Runs the control update-configuration command on the primary cartridge.
4. Starts all secondary cartridges in the application.
5. Runs the control deploy command on the primary cartridge.
6. Runs the deploy user action hook, if present.
7. Starts the primary cartridge using the gear start command.
8. Runs the control post-deploy command on the primary cartridge.
9. Runs the post-deploy user action hook, if present.