GroIMP wiki

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== Plugin deployment pipeline ======


In order to ease the deployment of Plugins and their version and to work properly with the [[dev-guide:plugin-ecosystem|Plugin ecosystem]], all plugins should follow the deployment pipeline, based on the docker image from: https://gitlab.com/grogra/groimp-utils/plugin-pipeline 

The pipeline is based on gitlab pages!

This pipeline goes through the following steps:

  - Download the previous version of the plugin from the repo-page
    - If no page is found or the 'rep' argument is used for run.sh the plugin.json from the repo is used
  - Prepare maven settings
  - Run mvn deploy -P app-with-doc and pipe the result into a file called 'log'
  - Execute the Summary_Parser to create create a new plugin.json file(plugin2.json)
  - Check if plugin2.json contains an url to a package. if not exit 1
  - Test if the new file contains more version than the one loaded in step 1
  - Pushes the created files to public which publishes them to the repo page

The published files contain the plugin.json, the embedded documentation, the SUMMARY.md and the maven generated files PANELS.md, IO.md, OPTIONS.md and COMMANDS.md.