16 docs tagged with "ci"

Although the content in this topics is relevant for this version of Deploy, we recommend that you use the rules system for customizing deployment plans. For more information, see Getting started with Deploy rules.

Using the Deploy Compare feature, you can compare two or more configuration item (CI) trees. In addition to comparing the chosen configuration items, it recursively traverses the CI tree and compares each CI from one tree with matching configuration items from other trees.

You can define control tasks on configuration items (CIs) to execute actions from the Deploy GUI or CLI. Control tasks specify a list of steps to be executed in order. There are two methods to parameterize control tasks:

You can add validation rules to properties and configuration items (CIs) in the synthetic.xml. Deploy comes with the regex validation rule, which can be used to define naming conventions using regular expressions.

Deploy's type system allows you to customize any configuration item (CI) type by adding, hiding, or changing its properties. These properties become a part of the CI type and can be specified in the deployment package (DAR file) and shown in the Deploy GUI.

You can define new configuration item (CI) types in Deploy. When you specify a new type, its base (a concrete Java class or another synthetic type), and its namespace, the new type will become available in Deploy. The new CI type can now be a part of deployment packages and created in the Repository browser. Each of the three categories of CIs (deployables, deployeds, and containers) can be defined this way.

In Deploy, you can define methods on configuration items (CIs). Each method can be executed on an instance of a CI via the GUI or CLI. Methods are used to implement control tasks, as actions on CIs to control the middleware. An example is starting or stopping a server.

Use the Deploy Explorer to view and manage the configuration items (CIs) in your repository, deploy and undeploy applications, connect to your infrastructures, and provision and deprovision environments.

Deploy features a modular architecture that allows you to change and extend components while maintaining a consistent system. This is a high-level overview of the system architecture:

The repository object in the Deploy command-line interface (CLI) allows you to export the Deploy repository tree to a ZIP file that can be imported into the same Deploy server or into another Deploy server. The ZIP file contains all configuration item (CI) properties, including artifact files.

Deploy stores all of its information in the repository. The Explorer gives you access to the configuration items (CIs) in the repository and allows you to edit them manually.

Functionality in the Deploy server can be customized by using plugpoints. Plugpoints are specified and implemented in Java. On startup, Deploy scans its classpath for implementations of its plugpoints in the com.xebialabs or ext.deployit packages and prepares them for use. There is no additional configuration required.

You can use the Deploy rules system and a PowerShell script to find and update the value of a previously deployed property with a new deployed property value.

The Deploy command-line interface (CLI) provides objects that you can use to interact with the Deploy server.

This is an overview of the types that are available in the Deploy command-line interface (CLI).

When using the Deploy command-line interface (CLI)