Skip to main content
System StatusContact Support
VersionOne Community

Configuring Continuum Flow Plugins

Overview

Since each plugin performs different types of operations, the specific configuration settings for every plugin will be different.

This article covers the initial configuration of the official plugins included with Flow, and should provide guidance to anyone developing their own plugin.

Configuration Files

Plugins in Flow are managed by a combination of two different configuration files.

Local Plugin Config

First, each plugin has it's own config.yaml file, included within the plugins directory. The plugin's own config.yaml file includes settings about which data is relevant to display in the UI, which integration functions should be exposed to the Pipeline editor, the plugins icon, and so on.

The details of each plugin's config.yaml will not often change, except when the plugin is enhanced or expanded in scope.

Here's an example of the Jenkins config.yaml

# public functions are the ones that show up in the UI Pipeline editor.
public_functions:
  job.build:
    args_template:
      job:
      wait:

# base64 encoded icon is displayed in the UI
icon:

The public_functions section defines which functions in the various modules are available in the Pipeline. This allows the developer freedom to write code using as many functions as necessary, while only exposing a few to the Pipeline.

The icon setting contains a Base64 encoded icon for the plugin, and appears at various places in the Flow UI.

Global Config

The entire Flow application is managed by a global configuration. When logged in to Continuum as an Administrator, go to Administration -> Manage Plugins.

This configuration will contain site-specific information for certain plugins.

  • Was this article helpful?