The following list defines key terms:
Release A release is a repeatable plan that is used to drive deployments; it is IBM UrbanCode Release's core mechanic. A release defines the "what, when, and how" of a release.A release can occur at any point in the development-operations lifecycle. A releasee can represent a major event in the life of a company, or be a comparatively minor event, like a recurring maintenance release.
Release environment A release environment is a coherent logical unit into which software can be deployed. A release environment is composed of application-specific environments.
Application An application, as used here, refers to any business-meaningful piece of a system that can be independently deployed. Applications from all third-party integrations, such as IBM UrbanCode Deploy, are available for use. You can add any number of applications and applications from more than one third party can be combined into a single release.
Lifecycle A lifecycle contains an ordered list of phases that are associated with release environments.
Phase A phase represents a stage in the release process. Release environments are mapped to phases. A deployment is scheduled for a particular stage. You can customize the phases in a lifecycle to match how your applications move from the beginning to the end of the release cycle.
Gates A gate represents a quality requirement that must be met before a release can move to the next phase. Each gate has a target status; when the application has that status, the application can pass through the gate. For example, an application might need to pass certain tests or receive an approval.
Deployment A deployment is the activity of releasing software into a specific release environment. When you schedule a deployment, you select the release, the release environment, associated applications, and the deployment plan. Beginning at the scheduled start time, you and your team resolve the deployment's tasks.
Deployment tasks A task is a unit of work that represents some business-meaningful activity that is associated with a release. Tasks have start and end times. Tasks can be manual or automatic. Typically, automatic tasks represent IBM UrbanCode Deploy application snapshots.