UrbanCode Release uses standard system development life cycle and project management methodologies and practices. The following list some important terms:
-
release A release is a repeatable plan used to drive deployments; it is UrbanCode Release's core mechanic. A release defines the "what, when, and how" of a release—it identifies the applications that will be released; specifies when release events will occur; and, finally, defines tasks and the order in which they will be performed. A release can occur at any point in the development-operations life cycle, 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 uDeploy, 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 associated with a release. Tasks can be added manually to scheduled deployments or be imported through CSV files.
