Motivation
Currently, the CI uses a monolithic approach to build all the plugins, installing the dependencies needed by the build process of each plugin in a shared environment, and building all the plugins in that shared environment. This sometimes prevents different plugins to depend on different versions/configurations of the same tools. Moreover, it doesn't allow to optimally isolate the environment (i.e.: a plugin build environment is polluted with dependencies coming from other plugins).
Feature
Creating a modular CI, composed of reusable workflows that can be used to build different plugins independently and, at the same time, in an isolated environment.
Alternatives
Additional context
Motivation
Currently, the CI uses a monolithic approach to build all the plugins, installing the dependencies needed by the build process of each plugin in a shared environment, and building all the plugins in that shared environment. This sometimes prevents different plugins to depend on different versions/configurations of the same tools. Moreover, it doesn't allow to optimally isolate the environment (i.e.: a plugin build environment is polluted with dependencies coming from other plugins).
Feature
Creating a modular CI, composed of reusable workflows that can be used to build different plugins independently and, at the same time, in an isolated environment.
Alternatives
Additional context