* The Bcfg2 server is responsible for taking a comprehensive infrastructure description and turning it into a series of configuration specifications for particular clients. It also manages probed data and tracks statistics for clients. The Bcfg2 server takes information from two sources when generating client configuration specifications. The first is a pool of metadata that describes clients as members of an aspect-based classing system. That is, clients are defined in terms of aspects of their behavior. The other is a file system repository that contains mappings from metadata to literal configuration. These are combined to form the literal configuration specifications for clients. * The Bcfg2 client attempts to reconcile the current configuration state with the configuration passed down from the server using various client tools. It does not perform any processing of the target configuration description. * Bcfg2’s reporting system is its killer feature. It allows administrators to gain a broad understanding of the configuration state of their entire environment. It summarizes * Configuration changes and when they were made * Discrepancies between the specification and current client states * Clients can be grouped by misconfiguration type * Configuration entries that are not specified * Overall client summaries according to these types

* WORKFLOW EDITOR * Configure your integrations in an easy to use UI * Your tools become the build steps in your workflow, which will run in the order you set them up. You can configure a build for building or testing, or sending out test releases, you can cover all your bases easily. * BITRISE.YML * Create and test workflows in your terminal * You prefer to work in your terminal instead of using a web browser? No problem! If you don't need your build logs to be on the web for the whole team to see, just install the CLI, download the config.yml from Bitrise and keep a tab in your terminal for Bitrise. * Continuous Delivery * You get your apps without the need of messing with manual controls. It’s like switching on autopilot. Lean back and order a scotch. * Code Security * Every build runs in its own virtual machine, and all data is discarded at the end of the build. We also hired sharks with laser beams on their head, just in case. * Hosted Environment - You don’t need your computer for building, go use it to binge-watch Breaking Bad instead. * Open Source - Oh, the steps you can use in your workflow? They’re open source. Modify, and share them as you like, or create a new one (if you think we were lazy bums, who missed an important service to integrate). * Customizable Workflows - We integrate with the services you love to use, like Slack, HipChat, HockeyApp and Crashlytics. Or you can generate random funny quotes, we’re not going to judge. * Support by Devs, for Devs - We don’t just have a support staff, we have Engineers, and you can talk to them whenever you want. Providing they aren’t on a space walk or having tea with a Klingon (a.k.a. virtually always!) * GitHub Pull Request support - If you are using a GitHub repository we are going to send the build's status to GitHub, so you can see it directly in your repository. Furthermore if you create a Pull Request we won't just test the fork or the feature branch, Bitrise will test the actual merged code too. * Over-The-Air App Deployment - We support a lot of third party beta testing and deployment services, but we wanted to provide an integrated solution to help you distribute your apps to your testers, without the need of registering yet another account after signing up to Bitrise.