

Jenkins and Travis CI compete in the continuous integration and delivery category. Jenkins is more flexible, while Travis CI offers a simpler, cloud-based solution. Travis CI stands out for its ease of use and efficiency in certain environments.
Features: Jenkins provides a vast plugin ecosystem, customizability, and integration with numerous tools. Travis CI offers seamless environment setups, GitHub integration, and is preferred for small to medium projects focusing on simplicity and speed.
Ease of Deployment and Customer Service: Jenkins requires manual setup, offering extensive customization, and demands more technical expertise but provides greater control. Travis CI has a straightforward deployment process with a cloud-based model, is appealing for quick setups, and its simplicity is favored for quick resolutions.
Pricing and ROI: Jenkins is open-source, leading to lower initial costs but potentially higher long-term investment in management. Travis CI typically involves service fees, offering predictable costs and faster deployment, resulting in quicker ROI. Jenkins provides value through its customization options, while Travis CI delivers predictable budgeting and easier scaling.
| Product | Mindshare (%) |
|---|---|
| Jenkins | 7.3% |
| Travis CI | 2.2% |
| Other | 90.5% |


| Company Size | Count |
|---|---|
| Small Business | 28 |
| Midsize Enterprise | 15 |
| Large Enterprise | 57 |
Jenkins is an award-winning application that monitors executions of repeated jobs, such as building a software project or jobs run by cron.
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.