Plug-ins

Plug-ins integrate IBM® UrbanCode™ Release with external products and tools.

Plug-ins connect IBM UrbanCode Release with external tools. After you install a plug-in, you run integrations to interact with the external tool. A plug-in might import data from the external tool, send data to it, or do both. For example, the IBM™ UrbanCode Deploy plug-in can import data from IBM UrbanCode Deploy, and then use the data to run IBM UrbanCode Deploy applications.

Plug-ins consist of distinct processes called steps. Steps have a varying number of properties, a command that runs the step, and post-processing instructions. Step properties can serve various purposes, from providing input to the command to supplying some or all of the actual command itself. Typically, each plug-in has one step that it uses to run integrations, although some plug-ins have separate steps for each version of the external tool that it integrates with. Plug-ins can have any number of steps that it uses for plug-in tasks.

Plug-ins can work with the plug-in tasks in deployment plans. Plug-in tasks can pass property values to external tools, and receive comments and status information in return. For information about creating plug-ins that work with plug-in tasks, see Plug-in tasks .

Plug-ins can subscribe to most notification events and respond when the events occur. For information about how to use events in plug-in steps, see Plug-in task events.

Many plug-ins are available for you to download and install. For information about the available plug-ins, see UrbanCode Release Plug-ins on the UrbanCode Developer website.

You can also create your own plug-ins. For information about creating plug-ins, see Creating plug-ins.

For information about installing plug-ins, see Installing plug-ins