Mojo Benefits for SCM Administrators

OpenMake Mojo facilitates and coordinates the handoff of the build to release process between development teams and central SCM.  Using the workflow capabilities of OpenMake Mojo, development teams can define the pre and post build tasks that must execute around their build scripts so the SCM team can re-execute the process.

Mojo Key Benefits for SCM administrator include:

Coordinated Hand-offs

OpenMake Mojo's build process automation allows development teams to create their application life cycle process and then promote to SCM for execution and control.

Centralized Logs and Reports

OpenMake Mojo centralizes logs and reports so both SCM and development teams can see and review results.  Results can be emailed to all parties involved for easy access and decision making.

Shared but Separate

OpenMake Mojo gives the control of defining an application life cycle to both developers and SCM administrators separately.

Secured Processing

OpenMake Mojo secures build processes that execute on production machines ensuring that developers can only execute what they have access to on their own development machines.

Simplifying Multiple Steps

OpenMake Mojo helps simplify the execution of multiple activities that are necessary for releasing an application into production.

Bill of Material Reporting

OpenMake Mojo is integrated with "best of breed" open source and commercial source code management tools allowing you to run a "bill of material" report prior to the execution of your build step.  This shows what source code has been retrieved just prior to the running of your build scripts. For a more complete Build Audit Report, OpenMake Meister Insight integrates at a deeper level showing not just what was "checked-out" prior to a build, but what the compiler actually used.

Standardized Calls to ALM Tools

OpenMake Mojo integrates with both open source and commercial application life cycle tools for standardizing on the ways these tools are called and executed in a precise order.

Testing and Static Analysis Integrations

Requirements, Testing, and Deployment Tool Integration
CA Software Delivery
Bugzilla
Checkstyle
Crap4J
Doxygen
Emma
FindBugs
IBM ClearQuest
IBM Tivoli
InstallShield
Japex
Jira
JUnit
JCoverage
JDepend
Nunit
Manage Ear and War Deployment Descriptors
MD5 Checksum for executable validation
PMD
Serena Tracker
Serena Mover
Wise Installer

SCM and Build Scripting Integrations

Software Configuration Management Tool Integration
Accurev
CA SCM (Harvest)
CVS
IBM ClearCase and Team Concert
Microsoft Team Foundation Server
Microsoft Visual SourceSafe
MKS Source
Serena PVCS
Serena Dimensions and Dimensions Express
Perforce
Borland StarTeam
Subversion

 

Build Scripting Support
Maven, Ant, NAnt
Make, NMake, CMake, EMake, OMake, IMake
Python

 

Simple Licensing Model

OpenMake Mojo delivers enterprise scale continuous integration and distributed workflow through a simple licensing approach. Mojo Standard is available for free, unlimited use, so that your team can begin using Mojo today at no cost.  As your needs grow, you can upgrade to  Mojo Professional or Mojo Enterprise offering  simple, bundled packages to expand your build farm for distributed processing with Remote Agent technology at an affordable price.

Mojo Standard

  • 1 Remote Agent, FREE
  • $399 yearly maintenance

Mojo Professional

  • 5 Remote Agents, $2,495
  • $1295 yearly maintenance

Mojo Enterprise

  • 25 Remote Agents, $7,995
  • $3,995 yearly maintenance

Customer Success Stories

100% Build to Deploy automation that is Developer Driven

See how American Family Insurance implemented a secure, developer driven, build to deploy process using OpenMake Meister and CA SCM r12. This demo was presented at CA World 2010 and at the CA technologies Global Lifecycle User Group Quarterly meeting in September of 2010. This demo has an excellent example of how Meister 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 for 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