Collaborate between Development and Production Operations

Keeping teams in sync requires the ability to pass IT requirements from Development to Production Operations. Meister supports collaboration using a promotional process that allows developers to define the IT requirements but hand off control to Production Operations.

Support Agile Development

Meister's Continuous Integration server supports the agile process of frequent code integrations.  Use Meister's CI server to create build to release workflows using "out of the box" plug-ins for version control and testing -  or call any command script or program that you need.

Eliminate Machine Configuration Drift by Leveraging Cloud Environments

Meister CloudBuilder allows you to automatically construct and deconstruct server images as part of the DevOps process. Leveraging Cloud images eliminates the drift in machine configuration between development, test and production. "It worked on my machine" is a common phrase that can be eliminated by automating the provisioning of Cloud environments.

Increase DevOps Efficiency and Reduce Hardware Cost 

DevOps activities can span compiling objects, executing test and performing deployments.  Meister improves this process by allowing you to define server clusters or pools to each activity in the DevOps workflow.  Machine utilization can be configured so your process is executing in the most efficient way possible.  Meister DevOps supports virtual environments as part of the Clusters to help reduce the cost of physical redundant hardware.

Improve Success Rate of Software Builds and Deployments

Meister's Dynamic Framework standardizes the logic of builds and deployments allowing enough flexibility to support the unique requirements of each team.  By eliminating the one off script driven processes for build and deploys, Meister improves the success of your builds and releases.

Improve the Visibility of your DevOps Process

Remove dependency on "black box" scripts and processes using Meister's Dynamic Framework.  Meister's Framework allows you to centralize all steps, parameters and configurations for your build to release activities.

Support more Frequent and Smaller Software Releases

No need to build and release all objects every time you perform a release. Reduce risk by knowing what objects have been impacted by a change. Meister's Dynamic Framework allows you to  Build, Test and Release only the impacted modules avoiding unnecessary risk of full builds and releases.

Reduce Confusion by Centralizing Configuration Management Across the Software Life Cycle.

Allow developers to clearly communicate configuration parameters for moving software through the Dev, Test, Release environments. Meister tracks and automatically updates detailed configuration information for running builds, executing test and deploying your software across the software life cycle.

DevOps for the complete Life Cycle

Builds and releases need to be executed across the lifecycle, even when you are working in an agile environment. Seldom is there the case where only one version of the application is used. For example, development is always newer than production. When production breaks, new features should not be included in an emergency fix just because the build can only be done at one lifecycle phase. Meister allows you to perform builds and releases that support a life cycle environment, including Emergency builds and releases.

Accelerate Your  Builds for faster processing

The compile and link process - referred to as a software "Build" is all to often the bottleneck, particularly in agile environments where the build is executed frequently. Meister's Dynamic Framework allows you to execute builds in parallel reducing build times by as much as 50%.

Extend IDEs

Extend the IDE automatic code creation functionality directly to your builds. Even when you refactor, Meister monitors the IDE project files and performs the build refactoring for you - now that is build automation! View a Quick Demo

Schedule Build to Release Processes with Email Notification

Schedule your builds and workflows to execute at anytime of the day or night. Use email notifications to alert the team of the scheduled builds success or failure - sending them the html link right to the build logs.

Establish Standards using Reusable Build and Deploy Services

Your hard work in writing build and deploy scripts should not be wasted - with Meister's Dynamic Framework, you can create reusable build scripts, called Services that can be reused and shared.

Administer Users and Groups

Define Users and Groups and assign priviledes using Meister's Administration. The administration features allows you to restrict build and workflow executions to certain Users and Groups. You can also restrict who can be defined to standardize build best practice and control what dependency directories can be referenced in builds.

Define Build and Deploy Best Practices

Repeatability in the Build and Deploy process is achieved by defining standards that can be shared across teams. Through Build  and Deploy Services, best practices can be defined and implemented across the enterprise. Best practices ensures that when you build and deploy a jar, war, ear, dll, exe of a certain type, that it is perfomed the same way each time.

Secure Your Builds

Extend the Administrative features of Meister by extending the Meister privileges features to LDAP security. Meister supports LDAP to provide the tightest control and security possible over you build to release process.

Build Audit and Impact Analysis

Build Audit Reports provides you micro level details of your builds such as compile options used and dependency directories used during builds.  You also get Build Metrics reports and centralized logging.

DevOps Metrics

Centralized logging, Build Difference Reports, Metrics Reports and Graphs are just a few of the reports that Meister provides. These reports track the progress, time measurement and results of your DevOps steps.

Life Cycle Support

Builds and releases need to be executed across the lifecycle, even when you are working in an agile environment. Seldom is there the case where only one version of the application is used. For example, development is always newer than production. When production breaks, new features should not be included in an emergency fix just because the build can only be done at one lifecycle phase. Meister allows you to perform builds and releases that support a life cycle environment, including  Emergency builds and releases.