To create an environment gate, specify the conditions that
must be met before component versions can be deployed to the environment.
Before you begin
Create one or more component version statuses. See by clicking and then under
Version Statuses,
click
Add Status.
Procedure
- Display the Environment Gates pane
for the target application (). This
pane lists the environments and the gates for each environment.
- Next to an environment, select a value from the Add
a new condition list.
The available
statuses are defined in the default.xml file.
The default statuses (Latest, Passed Tests, Archived)
are supplied as examples; in most cases, you supply your own values.
Selecting
a value provides both And and Or selection
boxes.
Using the And box
adds another value to the condition that must be satisfied. For example,
if you define a gate with the conditions Passed Tests and Latest,
only component versions with both of these statuses can be deployed
into the environment.
Using the Or box
adds another condition to the gate. Additional conditions are defined
in the same way as the first one. A gate with two or more conditions
means that the component version can be deployed if it meets any of
the conditions. For example, if you define a gate with the conditions Passed
Tests and Latest, a component version passes
the gate if it has either status (or both). A single gate can have
any number of conditions.
- Repeat these steps for other environments. Each
environment can have different gates.
- Click Save Conditions to save your
changes.
Results
Now, component versions can not be deployed to the environments
unless they have the specified statuses. To assign statuses to component
versions, see
Component version statuses.