Elements of Release Automation

Release Automation elements include the following:

Property	Description
Components	Components are the building blocks of Release Automation. They represent deployable items and have user-defined component processes that operate on those items. After defining a component's source and processes, you import its artifacts into the Release Automation artifact repository, CodeStation, to store component versions.
Applications	Applications initiate component deployments; they bring together components with their deployment targets, and orchestrate multi-component deployments. When you create an application, you identify the included components and define an application process. You can create a snapshot to capture the application's current state, and as the application moves through different environments, the snapshot ensures that proper component versions are used.
Environments	An environment is a user-defined collection of resources that host an application. Environments are typically modeled on some stage of the software project life cycle, such as development, QA, or production. A resource represents a deployment target, such as a physical machine, virtual machine, database, or J2EE container. Components are deployed to resources by their managing agents, which are physical processes.

Property

Description

Components are the building blocks of Release Automation. They represent deployable items and have user-defined component processes that operate on those items.

After defining a component's source and processes, you import its artifacts into the Release Automation artifact repository, CodeStation, to store component versions.

Applications

Applications initiate component deployments; they bring together components with their deployment targets, and orchestrate multi-component deployments.

When you create an application, you identify the included components and define an application process.

You can create a snapshot to capture the application's current state, and as the application moves through different environments, the snapshot ensures that proper component versions are used.

Environments

An environment is a user-defined collection of resources that host an application. Environments are typically modeled on some stage of the software project life cycle, such as development, QA, or production.

A resource represents a deployment target, such as a physical machine, virtual machine, database, or J2EE container. Components are deployed to resources by their managing agents, which are physical processes.