Automating Your Compile and Link Process

Meister includes the ability to both manage your Workflow process, and drive down into the compile and link process to automate the Build step of your Workflow.

Automating your Builds involves invoking two steps. The first step is the generation of your build script, the second is executing the build.  Meister is capable of performing both steps, removing the manual effort of writing Make, Ant, or Maven build scripts.   A command line program called bldmake is used to generate your build scripts.  It uses the Build Service, Build Method and Target information as input.  The output is a build script, called a Build Control File. 

Once your Build Control File is generated, you can use it as often as needed by passing it to the command line program called om. om will read the Build Control File and execute the compile, link, jar, war, ear processes needed to build the Target.  In addition, it will perform deep dependency scanning – called Dependency Discovery – to track all artifacts used in the build, regardless of their location.  A version control tool is not needed to perform the Dependency Discovery.

This guide provides you details on how to call both the om and bldmake programs from a command line or from the Workflows providing you the ability to define your build process from a continuous integration methodology to an on-demand build.

Tutorial Help: View an online demo on executing a Private Workflow with a Meister Build, or executing a Build from the Command Line.