Jenkins vs Travis CI comparison

"For business needs, Jenkins is the most relevant choice because it can be self-hosted, the price is good, it’s robust, and requires almost no effort for maintenance."

"Jenkins has built good plugins and has a good security platform."

"Jenkins's automation and orchestration features have significantly improved workflows by automating various processes. Initially, it did not support YAML manifesting or GitOps, but recent versions have introduced these capabilities. Now, the tool supports importing manifest files from Git repositories, enabling the implementation of GitOps pipelines. Compared to other tools like GitLab, it has become a mature tool for running CI/CD pipelines."

"The most valuable features are Jenkins Pipelines for ALM and full Deploy Cycle."

"We significantly reduced build times of large projects (more than 80k lines of Scala code) using build time on Jenkins as a time sample. It reduced the developer write-test-commit cycle time, and increased productivity."

"The most valuable feature of Jenkins is its continuous deployment. We can deploy to multi-cluster and multi-regions in the cloud."

"I can install Jenkins for integration from multiple developers and automate application delivery, staging, and production environments."

"Jenkins is very easy to use."

"The only thing I like about Travis CI is that you have a YAML file to define a Travis flow."

"Jenkins could have better cloud functionality. Currently, we are using the existing legacy model, but we are moving toward the cloud, so it would be great if they could improve in that area. In the future, I would like more cloud features and related training materials, like a video tutorial."

"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."

"Jenkins can improve by continuing to add additional plugins for all the new solutions that are coming out within the cloud sphere."

"Jenkins is not an easy solution to use and the configuration is not simple. They can improve the solution by adding a graphical interface that is more user-friendly."

"Tasks such as deployment, cloning, database switchover, and all other database missions and tasks are being done through Jenkins. If a job does not go through, at times the error message does not clearly indicate what caused the failure. I have to escalate it to the Jenkins DevOps team just to see what caused the failure. If the error message is clear, then I wouldn't have to escalate the issue to different teams."

"The UI must be more user-friendly."

"The support for the latest Java Runtime Environment should be improved."

"We need more licensed product integrations."

"The interface is very basic and not user-friendly; it feels like it was stuck in 2010."

"We are using the free version of Jenkins. There is not a license required to use the solution because it is open-source."

"We are using the free version of Jenkins. There are no costs or licensing."

"It's free software with a big community behind it, which is very good."

"Jenkins is open source and free."

"The tool is open-source."

"The solution is open source."

"There is no cost. It is open source."

"It is a free product."