Workflow Automation for Build Managers        

Build managers need power tools to keep up with the demands from developers.  Automation is key and workflow automation is a good place to start. 

Workflow automation manages the application lifecycle steps that are needed before and after the calling of build scripts such as Make, Maven or Ant. 

For 100% automation, build managers will benefit from the features of OpenMake Meister which includes all of the workflow automation of OpenMake Mojo Max plus full build automation features.

What Workflow Cannot Do 

Workflow solutions cannot perform distributed builds as the build scripts themselves control the calling of the compilers. Build scripts do not have the intelligence to sort out dependencies and understand how to orchestrate a distriubted build process.  Build automation is requried for this level of build processing.

Benefits for the Build Manager:

Self-documented Process

Each development team has their own requirements for running the workflows around their build scripts.  Without a centralized tool, Build Managers would need to follow email instructions or rely on out of date documentation to sort out how to re-execute a workflow process that a developer performed manually.  With OpenMake Mojo and Mojo Max, this information is defined to the central knowledge base and can be re-executed as needed.

Email notifications and Centralized Logs and reports

Once a build has completed, it is important for the information to get out to the developers quickly.  With Openmake Mojo and Mojo Max, all logs are centralized so developers know where to look as soon as the build completes and an email is sent to the team.

Open Ecosystem

It is not uncommon for each team to use their own tools and processes.  OpenMake Mojo and Mojo Max supports an open ecosystem allowing any tool integration through the command line interface or APIs.