Life cycles are used to control the flow of a release through its environments. See how to create a life cycle and use it for actions such as gating deployments and automatically deploying releases.
- [Narrator] Lifecycles are used to control the flow…of a release through its environments.…For example, you may want to make sure your app…is deployed to QA before it can move on to Production.…Lifecycle phases allow auto deployment…when a release is created.…And you can use retention rules to determine how many…releases to keep around.…Lifecycles are made up of phases which contain environments.…Phases are executed in order.…To move on to the next phase, you must deploy…to at least one environment in the previous phase.…
I say at least one, because the number of deployments…required in a phase is configurable.…Within each phase, you can configure auto deployment.…As soon as the lifecycle enters the phase,…the deployment will be triggered.…Let's head over to Octopus and see a lifecycle in action.…Lifecycles are under the Library menu.…Over to the left here there's a Lifecycle link.…When we start working with Octopus, a default lifecycle…is automatically created based on our environments.…
The bold items in the graphic represent phases,…
- What is Octopus Deploy?
- Working with the Octopus server and tentacles
- Using variables to scope configuration items such as roles and targets
- Installing and configuring Octopus Deploy
- Deploying a sample application
- Configuring a build server, adding a project, and creating a release
- Controlling release flow with life cycles and channels