Experts can be created using Groovy Script and simpler examples are given in the following KB articles. This article is a more comprehensive Groovy Script example that interrogates the changeset that makes up the delivery that the expert is being invoked on. It can be used as a template for developing your own Expert.
In this tutorial you will learn how to create a Deployment Automation plug-in that prints “Hello World!” to the console. The example Groovy and XML files are attached to this solution. Note:
1. A directory name to identify the plugin, under which the relevant plugin source and description files will exist 2. A . groovy files contains the source code that describes the actions of the plugin 3. Several .xml files that describe the plugin
The actual plugins code is stored in the agent's folder core\var\plugins. Each folder within core\var\plugins corresponds to the downloaded version of the plugin. If you want to see actual groovy scripts used in the plugin you can start from this folder.
In this document the following modifications will take place 1. An additional JSON file will be added to allow users to specify a property that can be used as a configurable parameter for calling the expert 2. Additional logic in the Groovy script to use the parameter supplied The following five steps will achieve this goal:
1. An additional JSON file will be added to allow users to specify a property that can be used as a configurable parameter for calling the expert 2. Additional logic in the Groovy script to use the parameter supplied Please note: The following resolution is specific to the 14.2 version of CM and this may well change for custom expert implementations in future versions of CM.
