Build Management Solutions for Change Management and Production Control  Are your Developers asking for Continuous Builds or Workflow Automation?Give them what their asking for - download MOJO for FREE today. Mojo supports Plug-ins for most SCM tools - review our SCM Plug-ins support. Bridging Development Source to Production Executables OpenMake Software maximizes your investment in an SCM solution by guaranteeing that your production executables are traceable back to your SCM repository. OpenMake Software offers our customer maximum protection from failed releases by providing the DNA and fingerprint evidence that links production back to its development origin. We guarantee that the SCM team can repeat the same build that was executed by the developers, without needing the developer to hand-hold the process. OpenMake Software provides the SCM team the knowledge and tools to take control of the software builds. Once you have your Source Code under control, it is important to establish a repeatable build that will manage your binaries. Most organizations execute the ad hoc build scripts that are provided to them by the developers. This process does not provide a clear audit of matching source to production executables, because it does not manage the binaries themselves. OpenMake Software creates a bridge that links production binaries back to the source code of origin. This critical step completes your SCM process as you can verify that the approved source code was indeed used to create the binaires that have been moved to your production environment. Separating Build Duties OpenMake Software provides a process that allows developers to "promote" their build to a production control team creating a separation of duties between development and production release. SCM administrators can enforce the use of "approved" source code and libraries in the production build, ensuring that no source code is released to production untested. CMDB SupportOpenMake Software’s dependency discovery data is the cornerstone to the Configuration Management Database (CMDB). Without it, source Information would be impossible to find, unless of course your manually read all the build scripts. Dependency Management and Impact Analysis OpenMake Software allows SCM administrators to trace project to project and project to infrastructure relationships, providing a predictive analysis of any software release. Our Build Audit reports provide a complete picture of how, when, and where the build was performed, enabling the build to be easily reproduced to support emergency release procedures. Build Best Practices OpenMake Software standardizes builds by allowing you to establish Build Best Practices throughout your organization. Build best practices creates consistency in the build process and better supports agile development activities such as continuous integration builds. If your developers talk about using Maven, they are attempting to standardize their builds. OpenMake Software standardizes builds for the enterprise supporting Java, Microsoft Visual Studio, LINUX, C-UNIX and z/OS. User Groups and Security Secure your pre-production build process using Meister's User and Group Security. Meister can be implemented with LDAP allowing you to create a build process that restricts certain Users or Groups from executing Builds and Workflows that touch a production or pre-production site. Enforce your separation of duties using Meister's User security and privileges. Build Audit with a Separation of DutiesAuditing Builds can be difficult if you have only the ad hoc scripts to rely on. With Meister full control of the build process can be handed to the Production Control or SCM teams, without the heavy load of thousands of make and ant scripts. All details of the build can be easily reviewed such as turning off debug flags, turning on optimization flags and the use of production versions of third party libraries to ensure production compatibility. This critical data is hidden in ad hoc scripts and is far from transparent. With Meister your builds can be executed with a full Build Audit report showing all artifacts used in the build, even when they are not under SCM control. See our Build Audit Report below. Notice that the file "rt.jar" was not stored in the ClearCase repository, but identified by Meister's deep dependency discovery and build forensics. 
SCM, Testing and Software Distribution SupportThrough Plug-ins, OpenMake Meister supports a wide variety of configuration management, testing and software distribution tools. Source Code Management and Deployment Plug-ins provide the out of the box integration with tools for creating your automated process workflow. Particularly important when defining a continuous integration process, SCM Plug-ins support check-in, check-out, bill of material reports, build difference reports, create label, synchronize, deploy, release, test, and email notifications Plug-ins are available for: AccuRev CA Harvest CA Software Delivery CVS IBM ClearQuest IBM ClearCase JCoverage JUnit Microsoft Team Foundation Server Microsoft Visual Source Safe MKS Source NUnit Serena PVCS and Dimensions Serena Mover StarTeam Subversion Perforce
|
