Deployment Request form
Create a deployment request for the update sets to be deployed to target instances.
| Field | Description |
|---|---|
| Release | The release that the deployment request is associated with. A deployment request can only be attached to one release. Note: Deployment requests are deferred if they aren't in the Ready for Deployment state at the freeze date. If the deployment request is deferred, a new release must be associated with the deployment request to reset its state back to Draft and successfully deploy. |
| State | The state of the deployment request, which is changed throughout the release process. See Deployment request states. |
| Source environment | The instance that contains the deployment request and its associated update sets. |
| Assigned to | Indicates the person who should receive task notifications related to the deployment request. Either Assigned to or Assignment group is required. |
| Assignment group | Indicates the group who should receive task notifications related to the deployment request. Either Assignment group or Assigned to is required. |
| On demand | Indicates if the deployment request should be released on demand, instead of scheduled.When On demand is selected, ReleaseOps creates a dedicated release that can only have this one deployment request attached. As soon as the deployment request's state is Ready for Deployment, it will be deployed. No freeze or release dates are followed for an on-demand release. |
| Configuration item | An optional association with a configuration item can be selected. This association doesn’t impact the behavior of ReleaseOps. |
| Deferred | Checked if the deployment request was deferred due to not being in the Ready for Deployment state by its associated release's freeze date. |
Parent Topic:ReleaseOps reference