You can add operational component processes to application processes, if the operational component processes do not require a component version. Operational component processes that do not require versions are listed in the step palette under the corresponding component. To learn about the different types of component processes, see Configuring component processes.
Field | Description |
---|---|
Name | A name for the step. Other process steps can refer to this step by this name. |
Ignore Failure | When selected, the step is always considered to have run to completion. |
Limit to Tag | Run the process only on the versions with the specified tag. |
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. |
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 application, the step runs only by the first online agent that is identified by IBM® UrbanCode Deploy. The mechanism that is used to identify the "first" agent is database-dependent (thus indeterminate). |
Precondition | A JavaScript script that defines a condition that must exist before the step can run. The condition must resolve to true or false. |
Run If Components Change | When this check box is selected, this step runs only if an agent resource that is mapped to this component has other component resource mappings whose inventories are changed by the process. You can select components and specify whether the step runs on all resources or only on the resources where components change. |