ExecutionEngine Documentation

Statements and Blocks

  • Last Modified: 2019-07-18

The execution engine interprets a deployment plan as a series of statements and blocks, in a top-down manner.

If you're comfortable with programming or scripting, you'll may be already familiar with how these blocks work. There is a Formal Specification available if you want to know precisely how the execution engine and plans/OtterScript work.


Blocks provide an easy way to organize your plans, and the sub-tasks those plans are made of. They can be nested as many levels deep as you need, and all blocks provide variable scoping (i.e. if you set a variable in that block, it will only be available within that block) as well as log scoping.

Log Scoping

BuildMaster's logs were designed to be as easy to navigate and understand as the plans. this is where collapsible log scopes come in:

  • Plan
  • Execution Log
IIS block
IIS block log

If you give a block a short description, then the plan's execution log will have a scope of the same name. This way, as you nest statements and blocks in your plans, they will have the parity in the log.

Because logs may contain sensitive data, such as the arguments to a command line, you can restrict users from viewing debug-level logs. This offers an ideal mix between security/compliance and visibility.

Assets in Plans

When an asset (template plan or script) is used in a plan, it is run as an operation, and can be treated in the same way (moved within a plan and have custom configurations). It is logged as an operation as well.

More on this topic:

Is this documentation incorrect or incomplete? Help us by contributing!

This documentation is licensed under CC-BY-SA-4.0 and stored in GitHub.

Generated from commit ce197caa on master