Add a Checkpoint to a Custom Plugin
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.
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.
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:
In Deploy you can create rules that define which steps should be included in a deployment plan. Each rule in the xl-rules.xml file defines a number of steps to add to the deployment plan. The available step primitives determine what kind of steps can be used. A step primitive is a definition of a piece of functionality that Deploy may execute as part of the deployment plan. For more information about Deploy rules, see Getting started with Deploy rules.
Deploy supports customization of the core product using the Java programming language. By implementing a server plugpoint, you can change certain Deploy server functionality to adapt the product to your needs. And if you want to use Deploy with new middleware, you can implement a custom plugin.
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.
This tutorial will explain the basic case of deploying a file to a target Container and doing something on the target Container with that file.
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.
The Deploy JEE plugin provides support for Java EE archives such as EAR files and WAR files, as well as specifications for resources such as JNDI and mail session resources.
The Lock plugin is a Deploy plugin that adds capabilities for preventing simultaneous deployments.
This example describes some classes from a test plugin we use at Digital.ai, the Yak plugin.