Java Architect at a tech vendor with 51-200 employees
Vendor
2017-02-22T12:00:36Z
Feb 22, 2017
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.
Search for a product comparison in Build Automation
Works at a tech company with 1,001-5,000 employees
Vendor
2017-01-18T12:44:10Z
Jan 18, 2017
- 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.
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.
Solution Management at a computer software company with 51-200 employees
Vendor
2015-03-03T07:54:29Z
Mar 3, 2015
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.
Build automation tools automate the time-consuming tasks inherent in creating a “build,” or usable version of an application. They automate and orchestrate the sometimes complex processes of compiling computer source code into binary code and packaging that binary code as well as running automated tests
Some PeerSpot members use build automation solutions. In reviews, they offer opinions on the most significant selection factors to consider when looking at this type of software. One theme...
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.
- 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.
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.
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.