Continuous Integration Workflows with Reuse is a Meister Benefit over Jenkins
Continuous Integration Workflows Reduces Redundant Work
We often get questions about the use of reusable workflows. OpenMake Meister supports the use of Reusable Workflows for both Builds and Deploys. Reusable Workflows allows you to define a set of activities that can be re-used over by other Workflows. This can be very handy in the deployment process in particular. Workflows that have reuse allows for granular organization of functionality and a high level of re-usability. A Reusable Workflow is defined in the same way as a Nested Workflow. The difference is in how they are used. A Reusable Workflow is a set of Workflow Activities that may be used in the same way by multiple Project Teams. Instead of re-defining these Workflow Activities for every Workflow, the Workflow can instead call another Workflow to perform those Workflow Activities. If you make a change in the Reusable Workflow, any Workflow that is using that Reusable Workflow will get the new changes at execution. When running the Workflow Monitor, you will see how each Workflow is called in the correct order, and you will see each step inside that reusable workflow execute.
Jenkins does not offer the ability to nest Workflows in this way. With Jenkins you must re-create the workflow for every team who needs it. Jenkins was not designed for large organizations with many teams. When you have defined a standard practice, you want to make sure everyone follows the practice. This is the purpose of reusable workflows. You can still use Jenkins, but allow it to call Meister for managing your build workflows. This way you are optimizing around Jenkins.
In order to use Reusable Workflows the Environment Variable OMSUBMIT_MAX_USER_PROC must be set to a value of 3. This must be set in the shell that launches the omsubmit executable. For Example: OMSUBMIT_MAX_USER_PROC=3