Components

Components use Component Processes to modify or deploy Artifacts to a Resource on an Environment.

Creating a New Component

You will be prompted for the following when creating a new component:

• Name - The title that will be applied to the new Component.
• Description - A description that will help users to identify Components.
• Template - Components may be created using a pre-configured Component Template, and are chosen here.
• Source Config Type - The SCM type that the Artifacts will be retrieved from.
• Import Versions Automatically - If checked, the component will periodically check for new Artifact Versions.
• Copy to CodeStation - If checked, a copy of the artifacts will be stored in the uDeploy repository.
• Default Version Type - determines whether the deployments are Full or Incremental. A full version contains all Component Artifacts. An incremental version only contains Artifacts modified since the previous version was created.
• Inherit Cleanup Settings - If checked, the Component will use the uDeploy server's pre-configured Cleanup Settings.

Component Processes

Creating Component Processes

• Name - The title that will be applied to the new Component.
• Description - A description that will help users to identify Components.
• Process Type - What the process will be doing.
• Inventory Status - The status that will be added to the inventory.
• Default Working Directory - The location where the work will be done.
• Required Component Role - The role required to execute the process.

Process Types

• Deployment - Deploys a component version to the target resource and updates the inventory after a successful execution.
• Configuration Deployment - configuration-only deployment with no component version or artifacts—simply applies the configuration (using properties, or configuration templates) to the target agent and updates the resource configuration inventory afterwards. Runs only if changes are detected.
• Uninstall - standard uninstall that removes a component version from a target resource and the resource's inventory.
• Operational (With Version) - operational process which does not add or remove any artifacts or configuration (and thus does not update the inventory); runs arbitrary steps given a component version. Useful when you want to start or stop some service for a previously deployed component version.
• Operational (No Version Needed) - same as the previous type, but does not require a component version. Runs even if no changes are detected.

Component Templates