Before you can run a deployment, you must define at least one environment that associates components with an agent on the target host. This initial environment is typically uncontrolled and often used to create snapshots.
Display the Create New Environment dialog Applications > [select application] > Environments > Add New Environment [button].
Enter the environment information in the fields provided:
| Field | Description |
|---|---|
| Name and Description | Name is used as part of the deployment process, and typically corresponds to the target environment. For example, if you are deploying to an integration environment, you may want to use the name "SIT". Description is optional text. |
| Require Approvals | To require an approval before components can be deployed to the environment, select this check box. If checked, Serena Release Automation will enforce an approval process before the deployment can be deployed to the environment. Initial deployments are typically done in uncontrolled environments, but once the deployment is successful, you can configure an approvals process as the application moves along the development pipeline. If you are setting up more than one environment, consider creating an approvals process for at least one of them. |
| Lock Snapshots | If you want all snapshots used in this environment to be locked to prevent changes, select the check box. |
| Color | Select a color to visually identify the environment in the user interface. |
| Inherit Cleanup Settings | Determines how many and for how long componenet versions are kept in CodeStation. By default, this check box is selected; the application will use the values specified on the System Settings pane. If unchecked, additional fields display: the Days to Keep Versions (initially set to -1, keep indefinitely) and Number of Versions to Keep (initially set to -1, keep all), which enable you to define custom values. |
Click Save.