OpenMake Meister

Defining a Private Pre-commit Workflow

In general, you should identify which validation steps you want to perform in your workflow, then decide which steps must be done before the build and which ones after.  Using the Workflow Explorer from the Meister GUI, define your Workflow.  Below are steps for creating Pre-commit Workflow:

1.  Create a new workflow from the Workflow Explorer, giving it a name and any other options.

2.  On the Detail Tab, add Activities.

3.  For each pre-build step, identify the workflow plug-in and appropriate activity template. If there is no activity template for the program you want to run, you can use the "Execute Shell Command" from the Activity list and enter the full command to execute for that step.

4.  For the build steps, first choose the Meister->Generate Build Control File activity template and enter your Project Name, Dependency Directory Name and other options, typically “-s” to enforce case sensitivity for Java and “-ov” for verbose output. 

5.  Next, choose one of the build execution activities like Meister->Execute Meister Incremental Build with desired options. Incremental build is the default setting and will provide you Build Avoidance for faster builds.

6.  For each post-build step, again identify the Workflow plug-in and appropriate activity template. If there is no appropriate activity template for the program you want to run, you can use the "Execute Shell Command" from the Activity list and enter the full command to execute for that step.

7.  Execute the Workflow. If there are errors, check the commands and run it again.