Applications, components, and generic processes share some process steps. This step applies only to application processes, including application processes that are associated with application templates.
| Field | Description |
|---|---|
| Name | A name for the step. Other process steps can refer to this step by this name. |
| Component Tag | A user-defined component tag that is used to select components. Only components with the specified tag are modified by this step. |
| Component Process | A process for the components that contain the selected tag. Only components that contain the process will run. Only one process can be selected per step. |
| Limit to Resource Tag | The user-defined resource tag that determines which resource runs the process. Only a resource with this tag, or a resource that has a parent with this tag, runs the process. See Adding tags to objects. |
| Use Versions Without Status | Restricts the components that can be used by the step. Components with the selected status are ignored. Available statuses: Active means ignore components that are currently deployed. |
| Max. # of Concurrent Components | The maximum number of components to deploy at one time. To deploy all components at the same time, specify -1. To limit the number of components that are deployed at one time, as in rolling deployments, specify an integer. In this field, you can use a value from a property, following the normal availability rules. See Property availability. UrbanCode Deploy attempts to resolve the value to an integer. If the value does not resolve to an integer, then the -1 value is used by default. Important: The maximum number of components that can be deployed concurrently is limited by the available resources on the deployment targets. |
| Max. # of Concurrent Jobs | The maximum number of component processes to run at the same time. To run an unlimited number of concurrent processes, specify -1. To limit the number of processes to run at once, as in rolling deployments, specify an integer. In this field, you can use a value from another process property. UrbanCode Deploy attempts to resolve the value to an integer. If the value does not resolve to an integer, then the -1 value is used by default. Important: The maximum number of component processes that can run concurrently is limited by the agent, based on the hardware configuration the agent runs on. |
| Fail Fast | If this check box is selected, the step does not start more processes after one process fails. |
| Run on First Online Resource Only | Instead of being run by all agents that are mapped to the environment, the step runs only on the first online agent that the server identifies. The mechanism that is used to identify the "first" agent is database-dependent, and thus indeterminate. If no agents are online, the server skips the step and marks its status as "Not Mapped." This setting may cause the environment to become noncompliant or to provide unexpected results, because only one agent runs the process, even if many agents are mapped to the environment. |
| Precondition | A JavaScript 1.7 script that defines a condition that must exist before the step can run. The condition must resolve to true or false. In the script, do not use the ${p:component.myProperty} notation. For example, to check the value of a component property in a component process, use properties.get("myProperty") == "myValue". See Property contexts for information about property access. |