This is follow up of version mismatch issue.

Ideally we would have a test failing when che.version != latest plugins in registry. but I don't have time to write that right now.

Here are two tests we can add:

a) if building crw server with che.version that doesn't exist in dependencies/che-plugin-registry/v3/plugins/eclipse/, run add_che_plugins.sh script to add them automatically

b) if building plugin registry and che.version in root pom is not found in latest files in dependencies/che-plugin-registry/v3/plugins/eclipse/, add the missing plugins by running script: https://github.com/redhat-developer/codeready-workspaces/blob/master/dependencies/che-plugin-registry/build/scripts/add_che_plugins.sh

that way a mismatch will be found in two places and we'll see red builds and fail emails.

—

In the plugin registry build, we should also run the script https://github.com/redhat-developer/codeready-workspaces/blob/master/dependencies/che-plugin-registry/build/scripts/add_che_plugins.sh during the Jenkinsfile https://github.com/redhat-developer/codeready-workspaces/blob/master/dependencies/che-plugin-registry/Jenkinsfile so that the plugins are added & committed BEFORE syncing from GH to pkgs.devel.

That would guarantee that for each new version of Che used in the crw serer root pom https://github.com/redhat-developer/codeready-workspaces/blob/master/pom.xml#L45 we also add the matching plugin version to the registry.

Might have to adjust the script to only add new plugins if they're not already present (so as to not add redundant commits that just update existing 7.14.3 plugins over and over for every CI build.