case study

configuration testing for build agents

Read Now

VersionOne had a classical case of configuration drift, which UpGuard allowed them to start correcting immediately.

VersionOne makes agile project management software. One of the strengths of their platform is the ability to give users everything they need in one place, which requires a large number of integrations between VersionOne and other tools. Developing those integrations means managing a geometrically growing number of test cases, and that requires having an effective DevOps strategy. VersionOne began using Chocolately and Jenkins to accelerate release velocity but by solving one problem they created another.

Configuration drift: not just for legacy servers

Ian Buchanan, Product Manager for the Platforms and Integrations team, realized that manual changes to build agents were creating new fragile artifacts. After talking with a DevOps specialist, he diagnosed the problem: configuration drift, the silent killer of release management.

The Cost of Complexity

Ian's team needed to test 1,600 builds per release cycle. With UpGuard they were able to automate the process of inspecting and validating the configurations of each build. What's more, UpGuard's visual interface meant the those tests were easily created and understood by new hires, removing a bottleneck that created unplanned, disruptive work.

Value in Visibility

With just the information from a basic UpGuard scan, Ian was able to get multiple agents running the same build again. The total return on investment, however, surprised even UpGuard. Read the whole story to see the statistics on how much work configuration drift creates and how simple it can be to eliminate it with UpGuard.

Read Now