Lesson 6: Scheduling deployments
Schedule a deployment for the Demo Release.
Scheduled deployments are added to the All Deployments page with a status of Not Started. After you start a deployment but before it is finished, it has the status of In Progress. When the deployment is finished, it has the status of Complete.
If you change the deployment plan after you schedule the deployment, but before you start it, your changes are added to the plan. After deployment starts, you complete the tasks that are defined in the deployment plan as they become eligible.
From the dashboard, click Releases and Deployments, and then click
The All Deployments page is displayed. The All Deployments page, as the name implies, displays all deployments. If the number of deployments is large, you can filter the list.
Click Add New.
You can also schedule deployment by using the Calendar.
In the Add New Scheduled Deployment window, in the
Release list, select Demo Release.
As you make selections, other fields that are related to your selections are displayed. The selected release determines the phases that are available for the deployment.
In the Phase list, select DEV.
The phase, which is derived from the lifecycle that is associated with the release, determines the release environments available to the deployment. Each deployment is run with a single phase.
In the Environment list, select DEV-1.
Release environments that are reserved for the selected phase are available. See for information about reserving release environments. A phase might have any number of release environments, and deployments can be run with any of them.
In the Deployment Plan list, select Default
The plan determines the deployment segments and tasks. Any plan that is associated with the release can be used. It is typical to have several plans associated with a release.
In the Scheduled For lists, select a date and time.
The start date and time is when you expect the deployment to begin. You can change these values after you schedule the deployment. After you start the deployment, IBM® UrbanCode™ Release tracks whether it is ahead or behind schedule.
Accept the default values for the other fields, and then click
If you include applications in a deployment, a Release Version can be especially useful. A release version, or snapshot, defines an environment, application versions, and quality statuses. When you select a release version, you automatically select the items that are defined in the version and do not have to select them each time you run the deployment. You can create release versions with the Pipeline view, or on the deployment's Application and Versions page.
In this lesson, you scheduled a deployment for the Demo Release and added it to the All Deployments page.
You schedule deployments by selecting a release and then choosing other items, such as phase and environment, from among the items associated with the release. The selected release determines the team that manages the deployment.
For more information about scheduling deployments, see Scheduling deployments.