Build Automation Features

Read what people say are the most valuable features of the solutions they use.
Steven Gomez says in a TeamCity review
Lead Engineer at a pharma/biotech company with 1,001-5,000 employees
TeamCity has a remote build feature that we have used to support legacy products (that use compilers that cannot run on current OS versions). Rather than having developers locked into an outdated PC for legacy support, we now only need to support a single VM that is configured as the build agent for the legacy product. TeamCity provides integrations for Eclipse, but in our case, it worked better to create a Python script that provided the necessary interaction between SlickEdit and TeamCity. Developers can make code changes on a current Windows or Linux system, and changes made locally are pushed to the build agent as a personal build. We are also exploring capabilities of use of the "Report Tabs". To ultimatly support FDA compliance concerns, I have a prototype of an HTML report being generated that includes CRCs, SCM URLs, SCM Revisions, etc for all items of a build chain. View full review »
Aaron Lord says in a TeamCity review
Web Developer and Software Architect at a tech vendor with 1-10 employees
The three best features are the following: * Automated builds triggered on check-in * Execution of unit tests with code coverage reports * Automated deployment to various environments. View full review »
Suresh Gururajan says in a CircleCI review
Full Stack Bot Engineer with 1,001-5,000 employees
Some of the most valuable features include container-based builds, integration with Bit Bucket (which our organization uses) and being able to store artifacts. In addition, it has the facility to encrypt environment variables, setup SSH into the build environment, clear caches and, most importantly, is the ability to configure a Circle.yml file which is easy to understand for most users who are not in DevOps, but also for developers. View full review »
Amit Cohen says in a TeamCity review
DevOps Engineer at a tech services company with 11-50 employees
VCS Trigger: Provides excellent source control support. Able to customize a feature with the specific conditions we want. For example, if we wanted only a specific branch to trigger a build, we can do that. View full review »
Michelle XIE says in a Jenkins review
Senior Automation Test Developer/Automation Test Architect at a software R&D company with 51-200 employees
Jenkins: pipeline/delivery pipeline and we can use shell script in the configuration. Jenkins has a lot of plugins. TeamCity: We can run automaton tests. View full review »
PauloBorges says in a Jenkins review
Senior IT Professional at a software R&D company with 1,001-5,000 employees
The most valuable features are Jenkins Pipelines for ALM and full Deploy Cycle. This solution fully integrates with a lot of other solutions like Git, TFS, Nexus, SonarQube, etc. View full review »
Cldengin57 says in a GitLab review
Cloud Engineer at a transportation company with 10,001+ employees
In GitLab, the most valuable feature is using information with a repository and using a containerized approach. You can use containers to create different jobs. The dashboard and interface make it easy to use. View full review »
Wasim Akram says in a Jenkins review
Managing Director with 11-50 employees
The most valuable features are plugins that make my server highly available. View full review »
reviewer1082187 says in a Jenkins review
Software Quality Assurance Team Lead with 11-50 employees
Currently, using Jenkins for automatic testing is the most valuable feature for us. It is very useful for us to be able to collect and manage automatic processing pipelines. View full review »
Oscar Urrego says in a Jenkins review
Software Test Automation Engineer with 1,001-5,000 employees
The most valuable feature is its ability to connect with different tools and technologies. View full review »
Alison Monteith says in a TeamCity review
Snr. Devops Engineer with 201-500 employees
The most valuable features are: * Build chains - it's really easy to set up all of your build dependencies * Snapshot dependencies and triggers - you always build the correct code as a snapshot is taken at the moment you run the build chain (i.e. no unexpected check-ins are included in your build!) * Templates - for setting standards and making the configuration easy and clean * Meta runners - sharing code TeamCity is very stable, is easy to set up and maintain. Once everything is configured there is almost zero time needed to maintain it. View full review »
Omar Granados says in a Jenkins review
Lider de DiseƱo y Arquitectura de Soluciones with 11-50 employees
There are a large number of plugins available for integration with third party systems. View full review »
Aimee White says in a CloudBees Core review
Website and EComm at a local government with 10,001+ employees
* Ease of access control (granular) * Scalability * Analytics View full review »
SeniorSofcae says in a CloudBees Core review
Senior Solutions Architect at a tech services company with 11-50 employees
All its technical features are valuable, but we could do 90 percent of those with Jenkins. The difference with CloudBees is when one of those features doesn't work, we can't figure it out, or it doesn't work the way we expect to there is somebody that we can contact who can make it work. View full review »
Lester Mead says in a CloudBees Core review
Cloud Engineer Specialist at Ameren Corporation
The product is all-in-one. It is based on Kubernetes, and we will be going to cluster, which is better. View full review »
AwsConte413b says in a Chef review
AWS Content Support Manager at a tech company with 51-200 employees
The most valuable feature is the language that it uses: Ruby. Regarding integration and configuration of the product, they're pretty manageable. The layers are really easy to configure. View full review »
Stefan Nava says in a Chef review
Director at a comms service provider with 10,001+ employees
Its most valuable feature is automation. View full review »
LeadDevO65cb says in a CloudBees Core review
Lead DevOps Architect at a tech vendor with 5,001-10,000 employees
The ease of use as far as getting it up and running, especially now that we have hundreds of applications wanting to go online and wanting their own built. We simply hand clients a CloudFormation template, and say, "Here is your account. We put the restrictions on your account. You can take care of yourself. If you don't like it, we will destroy and rebuild it." This allows us to focus on working with the developer on developer issues, not having to sit there and work through all the problems which come with setting up a pipeline, then setting up a Jenkins server, setting up GitHub hooks, and setting up everything else. It has helped us to really simplify our process. View full review »
DevOpsMa22d9 says in a CloudBees Core review
DevOps Manager at a tech vendor with 201-500 employees
* It has a wide variety of plugins. * It has a good reporting solution. View full review »
CEO2961 says in a CloudBees Core review
CEO at a tech services company with 1-10 employees
* Its scalability. * Ease of use. * The community and support available for it. Its ability to recreate our entire Jenkins environment, jobs, and seed jobs from code. Therefore, I could lose my entire Jenkins infrastructure all at once, and it could reconstitute the entire environment directly from code. View full review »
Mike Silva says in a Chef review
Senior Operations Engineer at a retailer with 10,001+ employees
Its versatility is the most valuable feature. It's not necessarily the end all or be all solution for configuration management, deployment, etc. However, for what we use it for, it fits right in and it doesn't bloat our infrastructure (or any of our instances) that we deployed to. View full review »
SrSystem0d4c says in a CloudBees Core review
Senior Systems Engineer at a media company with 501-1,000 employees
* Its integration with Slack. * Its integration with Git and GitHub. * The automated scheduling. * I like the script on AWS WorkSpaces. * It makes my job easier and does things that I don't have to do. The product is pretty well-integrated with the above products and our own platform. View full review »
ProjectA10de says in a CloudBees Core review
Project Architect at a manufacturing company with 1,001-5,000 employees
It works. It has easy connectivity for getting our pipelines into the cloud on AWS. We have no complaints, as it has always done what we wanted it to do. View full review »
Anshul Somani says in a Chef review
Solutions Architect with 201-500 employees
The community. View full review »
Timothy Rogers says in a Chef review
Engineer II at a transportation company with 10,001+ employees
It has been very easy to tie it into our build and deploy automation for production release work, etc. All the Chef pieces more or less run themselves. View full review »
Sign Up with Email