Real Solutions for Build Meisters
OpenMake Software provides real solutions for the build specialist. Unlike our competitor's solutions, we actually give you the tools to manage at the build engine level, such as MSBuild or Ant. We go far beyound just putting workflow around the static scripts. Build Meister's are the real power users of OpenMake Meister and many have become expert in the use of our Build Services and Build Methods for enforcing build best practices and decision making for a rock solid build process regardless of language or operating platform. OpenMake Meister is used by over 45,000 developers in over 400 installations. Reduce Scripting RedundanciesOne of the most important tools that OpenMake Meister offers build specialist is the ability to write highly reusable build scripts. OpenMake Meister allows build specialist to centralize build meta data into a centralized knowledge base and generate build scripts based on the Meister's Build Services reusable framework. This reduces the number of redundant build scripts that they must write and maintain from literally thousands of scripts to a small handful of reusable scripts. No Need for Re-writing Build Scripts Contrary to what our competitors would like you to believe - there is no need to re-write your Ant our Make scripts. In fact you can leave them just as they are, store them in a SCM tool and forget about them forever! With Meister, over 200 pre-defined Build Services are available out of the box for you to use and begin building with. These Build Services integrate with popular IDEs such as Microsoft .Net, Eclipse, IBM-RAD and Borland so that you simply define where your IDE project files are kept and Meister will re-generate your build script for you. In fact, your build process is improved as you keep your build scripts up to date, at all times, without having to manually update the scripts each time they become out of sync with the source code they are supposed to be building. So go ahead and refactor your code - Meister will fix your build scripts for you! Build ServicesOpenMake Meister's Build Services are the "power tools" needed to manage diverse build engines, administer dependency directories, define compile options, audit build artifacts and control builds across large enterprises without the need for working late, hiring more staff or relying on a particular key developer to get the job done. Using Build Services, build best practices can be defined and implemented with little effort as Meister does the job for you. Source Dependency ManagementSource code scanning to determine dependency relationship and "out of date" conditions should be a requirement of any tool that calls itself a "build management solution". OpenMake Meister does deep dependency discovery and provides a complete audit trail of every artifact that went into the build, even when the artifact did not exist in the build directory or was stored in a version management tool. Build Order Decision MakingUnlike our competitors who provide tools that simply do "job scheduling" of build scripts, OpenMake Meister manages at the build engine level, leveraging tools such as Ant and MSBuild. Because Meister manages at the build engine level it can determine the order in which builds should be executed even when circular dependencies are defined. It does this automatically, without the need for the build specialist to attempt to do this job manually. Dynamic Integration with IDEsBecause software changes rapidly, the build specialist often discovers that the build scripts that were just recently updated, are now out of sync with the changes being made by a developer. OpenMake Meister interoperates with the developer's IDE project file and automatically updates the builds running outside of the IDE – now that is a feature a build master can use! Workflow Activity Dependency Management and Continuous IntegrationOpenMake Meister and OpenMake Mojo provide powerful, time tested workflow automation with scheduling and continuous integration features. Define your pre and post build activities to create a build to release workflow and let Meister's or Mojo's workflow management and Continuous Integration Server handle the process. You can also create dependencies around the workflow activities so that if one step fails, a downstream activity will not execute. This can be used to build large systems where several applications are built in a particular order. For example, executing the build of the "data access" application before the "customer service" application. Extendable ALM PluginsOpenMake Mojo and OpenMake Meister come out of the box with several pre-defined ALM plugins supporting email notification, version control, testing and distribution tools. You can also define your own unique plug-ins to execute what your unique environment might require.
|
