Warning: preg_replace(): Compilation failed: invalid range in character class at offset 4 in /home/customer/www/openmakesoftware.com/public_html/wp-content/plugins/crayon-syntax-highlighter/crayon_langs.class.php on line 340
Warning: Cannot modify header information - headers already sent by (output started at /home/customer/www/openmakesoftware.com/public_html/wp-content/plugins/crayon-syntax-highlighter/crayon_langs.class.php:340) in /home/customer/www/openmakesoftware.com/public_html/wp-content/plugins/paid-memberships-pro/adminpages/reports/login.php on line 418 Meister Build Automation | OpenMake
Continuous Delivery Tools and Plugins for DevOps at Scale
Header Right
Main navigation
Meister Build Automation
Meister build automation accelerates compilation of your binaries to match the iterative and adaptive methods of Agile DevOps. Watch Video
Accelerate Binary Compilation
Scalable Build Processing
Accelerate CI with fast compiles and parallel processing using reliable dependency management across thousands of server pools. Meister reduces build times from hours to minutes.
Consistent Release Candidates
Standardize binary assembly for software builds that dynamically adapt to each version update. Our model-driven approach reduces or eliminates ad hoc scripting.
Expose all artifacts of your release candidate, even those not managed by a version control solution. Meister Impact Analysis and Audit Reports eliminate guesswork.
How it Works
1. Assign High Level Dependencies
Define the location of high-level source and library artifacts of each build Project. Like a VPATH, the Meister Dependency Directory can be ordered on a 'first found' basis to control code based on your build 'stream.'
2. Define Targets to Your Project
Generate a binary Target file, or define one using our Target Editor, using an integrated development environment like .Net or Eclipse. Meister equates a Target to a binary object.
3. Configure and Execute Workflows
Define Build Task order using a Meister Workflow. Generate a build control file, define pre/post-steps around the compile process, then execute using Meister's CI engine. Or, call from Jenkins, TeamCity or Bamboo.
4. Store and Audit
Store binaries in Meister's repository, or any external repository. Detailed audit reports, including explosion and implosion analysis, are created during your software build.
Priced on a 'pay as your grow' model so you can get started for as little as $6k per year for 10 apps with unlimited builds, users and workflows. Get your 30 day trial of Meister from GitHub.
Support Option
Receive engineer-to-engineer help and guidance from the experts at OpenMake. Standard and custom support options are available to match your specific needs.
Our continuous integration experts can help you define your mature continuous build process. Public or private custom courses and health checkups are also available.