BuildMaster Pros and Cons

For a software development manager like myself BuildMaster’s automation of the build and deployment processes is extremely useful. It optimizes the entire CI/CD process to ensure that software is released with standard and order. Review collected by and hosted on G2.com.

The reporting interface of the tool looks quite outdated and it is not very easy to generate reports that are relevant to my team based on the metrics which are most important to it. This makes it difficult for me to track and evaluate the performance of builds as I would want to. Review collected by and hosted on G2.com.

The back-end tie-in to Otter Script and the other components, as well as the ease of modification of any of the open-sourced component plugins. The process orchestration is top-notch; allowing fine-grained control on approval and security as well as detailed point-in-time manual intervention and restoration (depending on how you've written your pipeline!). The pipelines are 'drag and drop' for the newbie, allowing loops and conditionals, but also can be switched to pure code which is really well documented. Review collected by and hosted on G2.com.

The problem, the largest problem, is that the community isn't large enough to provide the scale of plugins that other solutions (I say that sparingly, as release automation is not the same as build automation) have. VSO, newest, has started implementing release automation and the backing behind it could cause a disruption unless the Inedo community pulls together. Review collected by and hosted on G2.com.