The auto-schedule feature is valuable. Another valuable feature is that Jenkins does not trigger a build when there is no change in any of the systems. Jenkins also supports most of the open-source plug-ins.
I have had no problem with the stability of the solution.
I like GitLab from the CI/CD perspective. It is much easier to set up CI/CD and then integrate with other tools.
TeamCity is very useful due to the fact that it has a strong plug-in system.
The most valuable aspect of the solution is its easy configuration. It also has multiple plugins that can be used especially for building .net applications.
It can do the CI pipeline well.
The most valuable features are compiling and deployment.
Permission separations mean that we can grant limited permissions for each team or team member.
It streamlined our deployments and system configurations across the board rather than have us use multiple configurations or tools, basically a one stop shop.
The orchestration, building the release, and then just executing it and managing that pipeline — the orchestration capabilities are great for that.
All features are useful. Our customer doesn't have any complaints about the tool. It works pretty well for what they want and what they need to do.
Very good reporting features.
What is Build Automation?
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 IT Central Station 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 that emerges from user comments is the importance of vendors that can keep up with the high pace of the technical evolution of the products that must be automated. Application development tools evolve quickly, so build automation must keep up. For some aspects of build automation, an Open Source community may be the best way to for tool makers and users to stay in sync with rapid changes in development platforms and development methodologies.
Build automation tends to get complex, so users prefer build automation systems that have simplicity in adding custom functions and rules and a simple, intuitive model for doing the core tasks. Others ask for build automation solutions that are simple but can be complex. Centralized build automation and a web-based front end can help with this goal. Making builds auditable allows multiple stakeholders to have awareness of how builds have been put together.
Given their essential interconnectedness, build automation suites thrive on APIs and plug-ins. The more, the better. Templates can keep things streamlined, allowing for consistent configuration on how an application Is built. Users also recommend build automation products that can delegate the building of executable code to a machine. Then, the tool should have the ability to trigger subsequent builds in a chain based off of multiple types of triggers in a deterministic fashion. Ultimately, the tool can enable an on-demand, push-button release strategy.