IBM® UrbanCode Release uses standard system development lifecycle and project management methodologies and practices. 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 identifies the applications that are released; specifies when release events occur; and, finally, defines tasks and the order in which they are performed. A release can occur at any point in the development-operations lifecycle, and 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.
Scheduled deployment A deployment is the activity of putting some piece of software into a release environment.
Deployment tasks A task is a unit of work that can represent any business-meaningful activity that is associated with a release. Tasks can be added manually to scheduled deployments or be imported through CSV files.