2015-02-23 07:24:00 UTC

When evaluating Build Automation, what aspect do you think is the most important to look for?

Let the community know what you think. Share your opinions now!
44 Answers
Real User

Easy to setup and configure. Good logging, alarm setting and support most of the build softwares. Also allow to add custom plugins to provide additional features and integration.

2017-02-22 12:00:36 UTC22 February 17

- works well with your build setup, can extract useful information when something breaks, and display/report it in a useful way.
- setup a useful pipeline shouldn't need days.
- good plugin infrastructure and maintained plugins.

2017-01-18 12:44:10 UTC18 January 17

The most important things are simplicity in adding custom functions and rules and simple, intuitive model for getting up and running (the core domain - tasks, dependencies etc.). Documentation is important as well, preferably with a lot of examples.

2016-04-01 11:47:01 UTC01 April 16
Real User

That would be the capability of the vendor to keep up with the high pace of the technical evolution of the products it needs to build/test/automate.

Secondly given that we are all using some kind of DVCS these days, its capability to handle complex multi repo automation supporting branch/feature builds.

2015-03-03 07:54:29 UTC03 March 15
Find out what your peers are saying about Jenkins, Chef, CloudBees and others in Build Automation. Updated: September 2019.
366,756 professionals have used our research since 2012.
Sign Up with Email