Deploy system

Revision as of 14:31, 9 December 2011 by Christopher (Talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search


The deployment system was designed to be an easy to use centralized tool to automate the deployment of executable product updates such as HeroBlade.

How to deploy an update

How it works

Things to keep in mind

Multiple people can connect to the Deploy Server at the same time and see the status; however only one product can be deployed at a time. If someone else is in the process of deploying something, please wait. You will see the status just as they do. Anyone has the option of hitting the Abort button to stop a deployment that is in progress.

The deploy client can safely be closed any time after the files are copied from your computer to the Deploy Server. This will not interrupt the process.

Freezing a Deploy

It is possible to prevent a product from deploying, by "Freezing" it. To do this, select the product in the Deploy Client, and click on the "Freeze" button. Enter in the reason for the freeze, and click "OK". This will turn the Deploy buttons blue, and inactivate them.

To unfreeze the product, click on the product, and then the "Unfreeze" button. This will display the dialog about why the product was frozen, and have buttons that say Unfreeze and Cancel.


A deploy can be aborted by using the Abort button. There is however a point of no return at which the process cannot be cleanly stopped. Once this point has passed, the Abort button will be disabled. This point is reached toward the end of the process when files on the launch server are changed.

The deploy server will automatically abort the process if something goes wrong at any point in the process, even if it is beyond the point of no return. For example if you try to deploy HeroBlade but are missing a required file such as SpeedTreeRT.dll the server will detect this and automatically abort the proccess.

If the deploy process is aborted past the point of no return, such as while the launch server was being updated, the cause should be quickly corrected and another deploy of that product done.

The process of adding a new product to the Deploy system

  1. Run Deploy.
  2. Click Edit button.
  3. Click Add Product buton.
  4. Select a product to inherit from. Example if you are adding HeroBladeBob and want to use version 1.25 of HeroEngine. You can inhert from HeroBlade_1_25_0_Base.
  5. Enter the name of the product you are adding.
  6. Click Create.
  7. Select the Product.
  8. Edit any values needed. Some common ones are in WISE_COMPILER_PARAMETERS
  9. Close the Config Editor.
  10. Deploy.

Talk about the parameters which need to be changed for a Linux deploy. ( WISE_COMPILER_PARAMETERS - LINUX_DEPLOY 1, WISE_LOCATION switched to the location of the RPM builder )

You can create a launcher file such as product.heal(make sure to use your company specific extention so that it works with your launcher).

Example contents:


(add information about updating deploy configurations)

See also

Personal tools