Variable usage example

For data that may change or that is not known in advance, Release provides a placeholder mechanism called variables.

This topic shows and example of a template that deploys an application to a test environment and assigns testing to QA. When testing succeeds, Release sends an email notification. If the testing fails, it tries again with the next version of the application.

This is the template:

Template with variables

The variable ${package} is used in the phase title and in the titles of various tasks. This variable is also used to instruct Deploy to deploy this package:

Variables in Deploy task

Click New Release to create a release from the template. Release scans the template for variables and asks the user to provide values for all of them.

Setting variables when creating a release

After the release is created, the release flow displays with the values of the variables filled in.

Note: You can still change variables by editing the fields on the Release properties page.

Variables in release

If the QA testing for BillingApp 1.0 failed and you need to repeat the procedure for the next version delivered by the Development team, you can click Restart Phase to restart the QA phase. Before the release flow resumes, you can change the variables of the release.

When the release resumes, the phase is duplicated with the new variable values in place. The old phase still has the old values.

Variables in restarted release