Jenkins vs Travis CI comparison

"Jenkins optimizes the CI/CD process, enhances automation, and ensures efficiency and management of our build and deployment pipeline."

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

"This solution has helped us in automating the build and test process, reducing time."

"The most valuable feature of the solution is its integration between different tools."

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

"Jenkins's open-based framework is very valuable."

"This is a great integration tool and very powerful."

"Jenkins is free and open source."

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

"Jenkins could improve the integration with other platforms."

"Jenkins should adopt the Pipeline as Code approach by building a deployment pipeline using the Jenkins file."

"Integrating Jenkins with other tools or solutions has presented some challenges. For instance, when attempting to integrate Jenkins with Kubernetes, I encountered numerous errors, which took several days to resolve. In Jenkins, adding a feature typically involves incorporating the repository feature separately. Jenkins lacks built-in Git repository functionality, necessitating an external Git repository to store Jenkins manifests."

"Better and easy-to-use integration with Docker would be an improvement."

"The solution's UI can use a facelift and the logs can use more detailed information."

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

"There are some issues with Jenkins, especially with the SIP job."

"The upgrades need improvement."

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

"Some of the add-ons are too expensive."

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

"Jenkins is an open-source platform."

"The pricing for Jenkins is free."

"I used the free OSS version all the time. It was enough for all my needs."

"The solution is open source."

"It could be cheaper because there are many solutions available in the market. We are paying yearly."

"In our company, we do pay for the licensing of the solution."