"It is saving time for developers, which is saving money for the company."
"The most valuable aspect of Jenkins is pipeline customization. Jenkins provides a declarative pipeline as well as a scripted pipeline. The scripted pipeline uses a programming language. You can customize it to your needs, so we use Jenkins because other solutions like Travis and Spinnaker don't allow much customization."
"With Jenkins, the pipeline will take your code from any versioning system like GitHub or Bitbucket. All the security scans can happen in one go and then all the tests also get run. You can just build one container in it and deploy it."
"Jenkins is very stable."
"The automated elements are easy to use and you can put them into your server."
"Has a good interface, is reliable and saves time."
"Very easy to understand for newcomers."
"Jenkins is stable, user-friendly, and helps with continuous integration. As of today, I can't see any tool that's better than Jenkins."
"Jenkins allows us to automate deployment, so I no longer have to do it manually. That's the primary use case. The other advantage of Jenkins is that it's open source. It was free for me to download and install. It's a product that's been in use for many years, so I can find a lot of support online for any issues that I may encounter while configuring anything for a given use case."
"Stability could be improved. I don't know the reason for the instability because there are no logs that help me to understand the problem."
"Jenkins can improve by continuing to add additional plugins for all the new solutions that are coming out within the cloud sphere."
"It could be cheaper."
"The documentation could be more friendly, and more examples of how to use it."
"There is no way for the cloud repositories to trigger Jenkins."
"For this solution to be a 10, it has to be a lot more stable. Maybe the public version of Jenkins is stable, but in our case it's not stable."
"There are a lot of things that they can try to improvise. They can reduce a lot of configurations. It is currently supporting Groovy for scripting. It would be really good if it can be improvised for Python because, for most of the automation, we have Python as a script. It would be good if can also support Python. We have a lot of Android builds. These Android builds can be a part of Jenkins. It can have some plug-ins or configurations for Android builds. There should also be some internal matrix to check the performance. We also want to have more REST API support, which is currently not much in Jenkins. We are not able to get more information about running Jenkins. More REST API support should be provided."
"Sometimes, random errors of metadata are not there, which causes delays. These are essentially gaps in the information being passed to the job."
"Its schedule builds need improvement. It should have scheduling features in the platform rather than using external plug-ins."
Incredibuild is ranked 11th in Build Automation with 1 review while Jenkins is ranked 2nd in Build Automation with 23 reviews. Incredibuild is rated 8.0, while Jenkins is rated 8.0. The top reviewer of Incredibuild writes "Saves time for developers, which saves money for the company". On the other hand, the top reviewer of Jenkins writes "We can do whatever we want and customize as much as we wish to in any programming language". Incredibuild is most compared with Bamboo, CircleCI and TeamCity, whereas Jenkins is most compared with Tekton, TeamCity, Bamboo, IBM Rational Build Forge and Digital.ai Release .
See our list of best Build Automation vendors.
We monitor all Build Automation reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
