Mojo Benefits for Development Managers

Continuous Integration and Build Process Automation provides your developers a job scheduling process for managing the application life-cycle steps around the execution of build and deploy scripts. OpenMake Mojo calls - in your custom pre-defined order - activities that are needed before and after the execution of the compile and link process, and centralizes and standardizes your development process.

OpenMake Mojo Key Benefits for Development Managers includes:

Maximize Productivity with Continuous Integration

OpenMake Mojo's continuous integration (CI) features allows a central location to define all pre and post activities around the calling of your build to deploy steps.  Mojo's Continuous Build and Continuous Deploy features support the triggering or scheduling of these activities in a consistent order, with chaining and "if/else" conditions around each activity called in the workflow. Common tasks can be executed and reused, freeing your developers to do the important work of software coding.

Shared Knowledge and Teamwork

OpenMake Mojo lets you visualize your development process, allowing all members of the development team to easily understand the steps in the application life-cycle. This shared knowledge keeps everybody on the same page, and enhances teamwork and productivity.

Team Handoffs

OpenMake Mojo makes it easy for your teams to hand off their application life cycle process to the change and production management teams who are responsible for releasing applications to production. With Mojo, all teams have the same view of the life-cycle process, and can automate the critical hand-off processes - reducing time-consuming errors and improving product quality.

Increased Productivity

OpenMake Mojo saves money by automating the calling of multiple application life cycle tools in a workflow process, eliminating the need for a single person to execute the steps, one at a time.  Mojo provides standard integrations with both commercial and open source ALM tools. OpenMake Mojo supports a centralized process for managing activities that are normally executed manually by multiple team members - enabling team members to focus more on feature development and less on the build process.

Metrics and Trend Reports

OpenMake Mojo tracks trends such as the most frequently executed build and deploy process, the longest running process and the most efficient processes.  These trend and metrics reports gives you a high-level view of problem areas that normally would be hidden under the cover of the black box scripts.

Requirements, Static Code Analysis and Testing Tool Integration

Bugzilla
Checkstyle
Crap4J
Doxygen
Emma
FindBugs
IBM ClearQuest
IBM Tivoli
InstallShield
Japex
Jira
JUnit
JCoverage
JDepend
Nunit

Build Script Integration

Maven, Ant and NAnt
Make
NMake
CMake
EMake,
OMake
IMake
Python

Customer Success Stories

Major Health Care Provider Centralizes enterprise builds with Meiter

See how a Major Health Insurance Provider implemented a centralized build process using Meister.

 

100% Build to Deploy automation that is Developer Driven

See how a Major Insurance Company implemented a secure, developer driven, build to deploy process using OpenMake Deploy+ and CA SCM r12. This demo has an excellent example of how Deploy+ with Remote Agents can parallelize the build to deploy process.

 

Meister added Transparency to the process...

"The implementation of Openmake Meister for build management allowed  BNSF to directly address one of their biggest challenges in the area of IT controls. This technology automated the team’s build processes, providing a  complete audit trail of changes, progression and approvals through each lifecycle stage. Finally, the implementation team used MKS Integrity Manager’s capabilities to manage the implementation itself." BNSF Technology Services Division - Learn More

Meister Standardized the compile process across the enterprise at UCLA ...

"UCLA's challenge was to standardize how builds and releases were processed, regardless of the development language used. OpenMake Meister provided this across the enterprise." University of Southern California, Production Control Team Lead - Learn More

 

Meister allowed developers to be more efficient saving money and time...

"As a company who specializes in process improvement we look for the most efficient ways to manage changing resources and requirements. We found this quality in Openmake Meister. Meister has allowed us to improve our development process by providing a streamlined, agile and 100% transparent build environment across the application lifecycle." Chris Lank, Ivis President and CEO, VP Worldwide Sales, Togethersoft

Meister accelerated builds across multiple remote machines...

"OpenMake Meister drastically reduced the cost of supporting our builds.  Meister allowed our build team to increase the number of builds supported using only 1/2 the staff, configured across 100 remote build agents."   Production Control, Major US Bank

Meister added consistency across multiple languages...

"Meister provides us a standard rules-driven build process regardless of platform, compiler and operating system. We selected Meister because it is the only enterprise-wide build tool that can thoroughly support our mission-critical Java, C/C++, and .NET applications.”   Todd Athorp, Sr Programmer, FIS

Meister allowed for more control in a 'fast evolving' development environment...

"Meister offers us increased productivity and quality  compared to manually controlled builds. Meister also completes the configuration management process through it's central build capabilities allowing Fortis to fully control all internal and external software assets within our fast evolving J2EE world.”  Matthias Pyck, Fortis Bank - Learn More