User guide

19
c. Select whether to use the Server or Gateway IP Address to uniquely identify the Server across
multiple networks.
2.9 Configuring Release Paths
Release paths are used to define the full path for distributing the release for diverse scenarios. For example, the
release path for a customer emergency might not be the same as the one for standard development. This also allows
the definition of who are the acceptance, deployment, validation and approvers of each stage.
1. In the main menu, choose Configure Paths. Then, in the sub-menu, choose Release Paths. The list of
active release paths will appear.
2. Choose the New button in the Release Paths list title bar. A form allowing you to define the new release
path will appear.
3. Enter the release path name and description in the Name and Description fields respectively.
4. Go to the Stages tab. This tab shows the list of stages defining the release path.
5. Choose the Add button to create a new stage. A new stage will appear at the end of the list. It is possible to
change the order of the stages using the Move Left and the Move Right buttons.
6. Select the stage type from the Stage dropdown. This will also load the Environments allowed for the
selected stage type. If the logged user does not have access to the Edit Approvals and Environment
permission or is not a release manager, he will not be able to modify the information of the stage.
7. Select the environment associated to the stage from the Environment dropdown.
8. Each stage is composed of 3 sequential steps (an Acceptance step, a Deployment step and an Approval
step). Here is how to configure each of these steps:
I. Acceptance step: During the acceptance step, the user selected as the approver in the Approver
dropdown will have the responsibility to approve or reject the deployment of the release in the
stage. This step can be automated by selecting the Automated check box.
II. Deployment step: The deployment step is composed of 2 parts: the deployment of the components
and the validation of the deployment which start after all components have been deployed
successfully. During the deployment part, the user selected as the approver in the Approver
dropdown will have the responsibility of the deployment and will receive email about execution
and failure of the deployment. During the validation part, the user selected as the validator in the
Validator dropdown will have the responsibility to perform basic tests to validate that the
components have been deployed correctly.
III. Approval step: During the approval step, the different users added to the Approvers list will have
the responsibility to approve or reject the release. Those approvals are not sequential; they are
done in parallel.
9. Repeat step 5 to 8 to add more stages to the release path.
10. Go to the Security tab and select all groups that will have access to this release path in View or Edit. You
can also decide to delegate management of the Release Path security to a group by using the Manage
Security check box.