Plugin deploy

This page discusses the process for getting a plugin installed in production It covers the following topics:

  • Plugin deployment process

  • Caching

  • Plugin usage

Deployment process

In plentymarkets, you cannot deploy individual plugins. Instead, you have to deploy a collection of plugins, a so-called plugin set. This is because during the deployment process, PlentyONE checks the source code of the plugins. The code check takes dependencies across multiple plugins into account.

The plugin build deploy process steps are visible in the UI when you perform a plugin build action.

Caching

PlentyONE uses Zend Opcache caching to increase performance. These caches can have an impact on plugin development because changes may not always be visible right away. There are three components that cache information.

Component Caching

Live shop

Always cached

Plugin set preview

Always cached

PlentyONE back end

Always cached
Caching can be disabled.

The Opcache is emptied every 7 minutes. The routes cache is reset every time you deploy a plugin set using the full build.

Usage limitations

Depending on how PlentyONE accesses the plugin, you may need to take additional steps for your plugin to run properly. The following table lists plugin integration options.

Use case Integration

plentyShop routes

Link the plugin set to a client, under ' Link clients ' in Plugin Set Overview. Alternatively, you can use the: Plugin Set Preview (eye button) in the desired Plugin Set.

PlentyONE back end routes

Link the plugin set to your user account, as a backend plugin set, under your backend profile settings.

Crons

PlentyONE only runs cron jobs of plugins if they’re installed in the plugin set linked to the standard client. The standard client is labeled in the Setup » Client menu.