Build managers need power tools to keep up with the demands from developers. Automation is key and defining a solid build process is a good place to start. Continuous Integration manages the application life cycle steps that are needed before and after calling build scripts such as Make, Maven or Ant.
Self-documented Process
Each development team has their own requirements for running the pre and post steps 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 build process that a developer performed manually. With OpenMake Mojo, 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, email notifications are sent to the team as soon as the build completes - with links to centralized build logs and any other information that you want to include. Whether a build succeeds or fails, Mojo lets your team know exactly where the build is in the lifecycle, so they can act fast to move your development proejcts forward.
Distributed Workload Processing
With complex systems often comes complex processes that need to be executed on multiple machines and operating systems. With OpenMake Mojo (Professional or Enterprise), the use of multiple Remote Agents allows you to distribute the workload of the build process across different machines (see diagram below).
It is important to note that Continuous Integration solutions cannot perform the distributed calls to compilers and linkers to improve the speed of the compile and link process. This is because Build scripts do not have the intelligence to sort out dependencies and understand how to orchestrate a distributed build process. OpenMake Meister can perform this level of Build orchestration and offers build acceleration that can reduce your build times down to less than 10 minutes.
ALM Tool Integration
It is not uncommon for each team to use their own tools and processes. OpenMake Mojo supports an open ecosystem allowing any tool integration through the command line interface or APIs. In addition, Mojo offers standard integrations to best of breed Application Life cylce tools.
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