13 BuildMaster Testimonials

“We are using BuildMaster, making progress towards our goal of using micro-services [BuildMaster] has definitely evolved a lot in good ways since I’ve been using it.”

"Within 90 days, we experienced tangible impact. We saved 160 developer-hours across 40 builds in a single month."

“It is pretty cool that both BuildMaster and Otter use the same InedoAgent service on servers.”

"They had confidence that when we said we were going to release a build for them, that it wasn't going to break, we knew exactly what was going to happen, and if something failed, we knew exactly what failed and how to fix it. All of this lead to greater increase in confidence, which then lead to deciding that we can release to production far more often and thus, more innovation is occurring."

"Large scale deployment can be a beast, that's why we've named BuildMaster; BeastMaster."

"Without BuildMaster we wouldn't have been able to do a lot of what we wanted to accomplish this year."

"We recently adopted a rule that we cannot deploy to any server without using BuildMaster, so absolutely its sphere of influence has grown."

"The reports BuildMaster can generate very clearly illustrate that we have done our job, how, when, where, and why."

“I spend more time finding the right command to deploy a .NET application than to embed it into BuildMaster.”

"When you move to something like Azure you have an environment that can be completely automated – that's the advantage of a cloud infrastructure. But it still takes a lot of work to do the automation. You need a tool like BuildMaster to leverage the theoretical advantages of the cloud. The combination of Azure and BuildMaster is a real winner."

“We’re trying to increase our cadence and do stuff rapidly while still following the rules. We found BuildMaster hit all the notes for us.”

"BuildMaster is playing a crucial role in fully automating the delivery of our software to the cloud."

“Deployment process was quarterly or tri-annual releases. And every time you did a release, somebody had to go into the Dev environment for the new release. And that was a half-day manual checklist to go through to get everything configured the right way. Now, all those checklists went away and we went to an automated script process to get things configured and installed.”