Overview

Build stages are parts of a project that are all executed when the project is built. Each stage can be configured to build its own recipe, on its own agent. Stages are executed independently and in parallel where possible (i.e. when there are agents available). A typical use for multiple build stages is executing the same recipe (or perhaps similar recipes) in multiple environments. This may include different compilers, operating systems, runtime dependencies and so on.

Default Stage

When you create a new project, pulse™ creates a default stage for you. This allows you to try out simple projects more easily. The default stage is configured to build the default recipe on any capable agent - this is any agent that has the required resources. For more complex projects, e.g. where multiplatform testing is required, you will need to add additional stages.

Note that built-in projects only have a single recipe, which is the default. Stages for these projects should always have a blank recipe field.

Properties

Build properties can be specified at the stage level. Properties specified on a stage apply only to that stage, and override any properties of the same name defind at the project level.

Required Resources

Required resources may also be specified at the stage level. These resources are only required for the stage, and are required in addition to the project's required resources. They can be used at the stage level to introduce stage-specific dependencies and properties. They will also affect which agents are capable of executing the stage.

Post Stage Hooks

Post stage hooks can be used to execute actions on the pulse™ master server after a build stage completes. These are just build hooks, that are triggered when the stage is complete, with properties specific to that stage available. For more information refer to the Project Build Hooks page.