A Typical Flow Using Release Packages Only

This section describes a typical successful flow using release packages without release trains.

The steps in this section assume that Release Control has been installed and configured, and that release elements have been created using the steps in Creating Release Elements.

Note: The flow you use in your implementation may be different.
  1. Create standalone or parent release packages.
  2. Optionally set up a release package hierarchy by adding child release packages.
  3. Add requests, deployment units, and deployment tasks to the release packages.
  4. Deploy, approve, and validate release packages through the test environments in the deployment path.
  5. Deliver production-ready release packages to the release engineering team for acceptance.
  6. Deploy and approve through the production deployment path.

After release package deployment to production is verified, the release packages are closed by the release manager or a release engineer.

Related Topics

Using Release Packages

A Typical Release Control Flow Using Deployable Release Trains

A Typical Release Control Flow Using Planning Release Trains