Executing Your First Meister Build

Builds are executed as part of a Workflow using a Workflow Activity. There are different pre-defined Workflow Activities that can be used to call build engines for executing your Build automation process.  Meister’s Workflow Activities can be found using the Workflow Explorer under “Add Activity” in the Workflow Hierarchy Section.  When you add a Workflow Activity a list box selection will display all pre-defined Workflow Activities.  By Selecting “Meister”, the following pre-defined Meister Workflow Activities will be displayed:

•     Executing Meister Incremental Build – executes a Meister Build using Build Avoidance.  Only the changed source and all dependent source and libraries will be re-built.

•     Execute Meister Incremental Build with Audit Report - executes a Meister Build using Build Avoidance.  Only the changed source and all dependent source and libraries will be re-built.  A Build Audit Report will be generated.

•     Execute Meister Clean All Build – Re-builds all objects regardless of their up-to-date status.

•     Execute Meister Clean All Build With Audit Report - Re-builds all objects regardless of their up-to-date status. A Build Audit Report will be generated.

•     Generate Meister Build Control File – Re-generate the Build Script prior to executing the Meister Build.  Recommended for all Builds.

The following Build sample will allow you to execute a Workflow that runs Meister’s Build automation.  It will also test your installation of Meister.  As you walk through this sample Workflow, you will learn the concept of a Meister Build Service.  A Build Service creates an executable of a particular type such as a .exe, .jar, .war, or .dll. This sample uses the Java Jar Build Service.