Plugins import strategies
This topic describes the strategies for importing plugins and plugin steps. The plugin import strategies define the conditions for upgrading plugins during replication import.
Note: Starting from Deployment Automation 6.3.3, plugins use Groovy 3.0.0 or later. Plugins with an old Groovy version do not run on agents 6.3.3 and later. To ensure improved security, we recommend that you always upgrade plugins to the latest version.
You can import plugins according to one of the following strategies:
|Upgrade all plugins||
This strategy enables you to upgrade imported plugins to the Groovy 3.0.0 or later versions available on the replication (source) or target servers. All the relevant processes are upgraded automatically.
If your replication file contains both old and latest plugin versions, but you plan to import processes that use only the old version, the system will detect the latest version in the replication file and upgrade your processes during import.
If an imported process uses a plugin with an old Groovy version, and the plugin with Groovy 3.0.0 or later is not available on the replication (source) or target servers, the import fails.
|Fail import for old Groovy version||
With this strategy, you can import only the latest plugin versions that use Groovy 3.0.0 or later.
If an imported process uses a plugin with an old Groovy version, the import fails.
|Import ignoring old Groovy version||
This strategy enables you to import plugins as is.
After you import data using this strategy, we recommend that you manually upgrade plugins. For details, see Load and upgrade plugins.
Tip: To verify that a plugin uses the latest Groovy version, open the plugin's info.xml file and check that the
groovy-version attribute displays version 3.0.0 or later. If the
groovy-version attribute is set to an earlier version or is missing from the info.xml file, the plugin uses an old Groovy version.