Adding Environments to Applications
After you create an environment, you add it to an application. Environments may be used by multiple applications.
Note: When you add a pipeline to an application, the environments in the pipeline are automatically added to the application. Environments that are part of a pipeline are grouped together in a section labeled with the pipeline name.
To add an environment to an application:
Navigate to Management > Applications > [select application] > Environments.
Click the Add Environment button.
Enter the environment information as follows:
Field Description Environment Select an environment. For information on creating environments, see Creating Environments. Require Approvals To require an approval before components can be deployed to the environment, select this check box. If selected, Deployment 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. Inherit Cleanup Settings Determines how many component versions are kept in CodeStation, and how long they are kept. If selected, the component will use the values specified in Administration > System > System Settings. If deselected, additional fields appear. Days to Keep Versions If Inherit Cleanup Settings is not selected, this field appears, which enables you to define custom values. This is initially set to -1, keep indefinitely. Number of Versions to Keep If Inherit Cleanup Settings is not selected, this field appears, which enables you to define custom values. This is initially set to -1, keep indefinitely.