Pipelines facilitate the procedures and approvals necessary for large and mission-critical changes, while also maintaining flexibility, and ease-of-use needed for any unscheduled, emergency deployments.
Pipelines are a series of stages consisting of environments, deployment plans, and many other optional features such as approval gates and configuration files. Stages can be a simple notification step where no environments are created, or tests run, or as complex as needed for any organizational requirement - including deploying to multiple testing servers with unique configurations and databases.
Pipelines as Code gives users the option to switch between pipeline visual view, and text view, making simple or complex changes effortless, and maintaining consistency across every release. In text view, you can simply copy code, and easily edit it if another release has similar, but slightly different requirements. You can also easily share pipeline configurations among team members, without having to take screenshots. Visual views provide an easy-to-understand, visual representation of your pipeline, while also being the "Code," behind your Pipelines as Code. Visual view and text view parody one another so users can switch back and forth as needed.
Deployment plans are at the heart of BuildMaster's automation, and are used to direct the execution engine. The powerful execution engine facilitates your entire release process, going beyond deployment automations. From coordinating a release with manual and automated approvals, to integrating with your current tooling, BuildMaster quickly becomes the strongest link in your DevOps toolchain.
From a simple, single operation deployment plan, to a complex deployment plan involving multiple operations and extensions, PowerShell integrations, and customized operation created via the BuildMaster SDK - plans provide all the directions necessary for automating the deployments of your simple and complex applications.
The visual editor provides a drag-and drop interface to build deployment plans one step at a time, allowing for the entire development team to know exactly what's happening to your release.
Modern Application Release automation is more than just moving a set of files from one location to another; it involves multiple quality control checks, database changes, specific server configurations, even manual interventions, while also needing to support multiple ways to go from code to production.
Gates are a mix of manual and automated approvals a release package must go through before production - they ensure quality and acceptability of a release. Before entering any stage in a pipeline, a release package must pass through that stage's gate. For example, if a package doesn't pass a set of automated unit tests, then it should not be advanced to the production stage since it is known to be a flawed package.
BuildMaster has built-in security and privileges with users directories. User directories are a collection of users and groups that add a level of granular control and security within BuildMaster. By associating users with a group or groups, organizations are able to permit and restrict access for specific individuals as needed.