Applications, components, and generic processes share some process steps. This step applies only to application processes.
This step runs the specified component process for all selected component versions, except the component versions that are already in the inventory. By contrast, the Run Process for Each Version step runs the process for each component version, whether or not each component version is in the inventory.
This step can install multiple incremental versions of the same component. To do this, use a single Install Component step in the application process. Then, when you run the application process, select multiple incremental versions to deploy. Beginning in version 6.2.1.1, incremental versions are deployed in the order that you select them in the Run Process window. To deploy the incremental versions in a specific order in versions prior to 6.2.1.1, create a snapshot, add the component versions to the snapshot in the order that you want to deploy them, and run the application process with the snapshot.
| Field | Description |
|---|---|
| Name | A name for the step. Other process steps can refer to this step by this name. |
| Component | Component that is used by the step; a step can affect a single component. All components that are associated with the application are available. To install another component, add another install step to the process. |
| Limit to Tag | User-defined roles can be used in processes; see Adding tags to objects. |
| 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. 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 number of component processes that can run concurrently is limited by the agent, based on the hardware configuration the agent runs on. |
| 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 scopes for information about property access. |