#1 most frequent
United States of America
41.5%20,189 installations of 48,630
What is Jenkins?
Jenkins is an open source automation server. Jenkins provides hundreds of plugins to support building, deploying and automating any project. As an extensible automation server, Jenkins can be used as a simple CI server or turned into a continuous delivery hub for any project.
Categories & Use Cases
Videos
Who Buys & Uses Jenkins
#2 most frequent
India
10.3%5,032 installations of 48,630
#3 most frequent
United Kingdom of Great Britain and Northern Ireland
5.1%2,504 installations of 48,630
Jenkins Powerful CICD Tool with Flexibility at the Cost of Usability
Use Cases and Deployment Scope
Jenkins is used for triggering builds in our company. We have more than 20+ apps which needs to be deployed , and we take help of jenkins to do so. From frontend, to backend to ML team, all uses jenkins for their deployment.
Jenkins helps us speed up our delivery by allowing parallel builds and testing, significantly improving deployment times. Jenkins integrates seamlessly with Git (GitHub/GitLab), Docker, Kubernetes, and other DevOps tools we use, enabling end-to-end automation.
Jenkins helps us speed up our delivery by allowing parallel builds and testing, significantly improving deployment times. Jenkins integrates seamlessly with Git (GitHub/GitLab), Docker, Kubernetes, and other DevOps tools we use, enabling end-to-end automation.
Pros
- Monitors source code repositories pretty well
- Automatically triggers the deployment when new code is pushed
- Advanced logic like conditional steps, parallel execution, or environment-specific stages
- Reusability across projects using shared libraries
Cons
- Complex UI
- Less user friendly
- Should not go down
- Plugin Dependency and Maintenance Overhead
- Limited Native Support for Modern Cloud-Native Workflows
Return on Investment
- Faster deployments
- Reduced Human Errors & Downtime
- Standardization Across Teams
- Initial Setup Time is more
Usability
Alternatives Considered
GitLab
Other Software Used
Cursor, WebStorm
The Power of Flexibility and Scalability for CICD Automation.
Use Cases and Deployment Scope
Jenkins integrates well with tools like Ansible, Terraform, Docker, and Kubernetes. Used to automate the build, test, and deployment processes across multiple teams, projects, and environments.
Pros
- Lots of plugins.
- Highly Configurable.
Cons
- UI/UX Feels Outdated.
- Steep learning curve.
Return on Investment
- Scalability.
- Improved Code Quality and Reliability.
Usability
Alternatives Considered
Atlassian Bamboo, GitLab and GitHub
Other Software Used
GitLab, Atlassian Bamboo, GitHub
Powerful CICD tool for handling all stages in pipeline with versatile programs.
Use Cases and Deployment Scope
We use Jenkins as a main
CICD in our project, we organize jobs with similar function into Group, we
create jobs for the build, compile, and unit test each time a developer
check-in their code to a specified branch and build a new version of artifact
when having master branch commit.
We add some additional
plugin and create Jenkins jobs for run system test, automation test, and
integration test automatically when having new commit to master and have jobs
for deploy our new code to destination VMs on demand.
Pros
- continuous deployment
- continuous integration
- continuous delivery also it's the best integration tools in the market
Cons
- Jenkins UI looks bit classic, and it is hard for manage when we have a large number of jobs and pipeline
- It does not have features for tracking job history, sometimes accident deletes or changes to a job and we unable to recover it.
- User and roles management needs some improvement
Return on Investment
- It made very good impact in business by fastening the process
- It provides single place for building all the jobs
- I don't see any negative impact from Jenkins
Usability
Alternatives Considered
GitLab
Other Software Used
PagerDuty, Docker, Oracle Cloud Infrastructure, Google Cloud Build
Jenkins : An opensource tool for automating software development and deployment
Use Cases and Deployment Scope
We are using Jenkins for continuous integration and continuous deployment in our organization. It has helped in moving towards automation and currently major applications created using TIBCO BPM Enterprise, React UI and Node JS are being deployed using Jenkins. Jenkins has helped a great deal to not just developers but system administrators as well. Any additional tasks which need to be completed along with deployment are added in the scripts which gets executed during deployment.
Pros
- Automated deployment
- It is open source and user friendly
- Customize deployment pipeline as per the requirements
- Supports good documentation
Cons
- There can be performance issues due to single server architecture.
- Implementation is not relatively easy
- User interface has room for improvement
- Redundant pluggins
Return on Investment
- Since Jenkins is open source, it saves licenses and procurement costs
- Manual tasks have been automated using Jenkins leaving ample time for users to focus on other tasks at hand
- Jenkins provides a wide range of plugins which can be used to complete deployment with ease
Usability
Alternatives Considered
Octopus Deploy, JFrog Artifactory and Bamboo
Other Software Used
Oracle SQL Developer, Postman, SoapUI Open Source, supported by SmartBear, Notepad++
Jenkins - Hard to use but can be set up to do anything
Use Cases and Deployment Scope
We use Jenkins to build and deploy all our applications. This range from web services, APIs, docker images, automated tests to small helper scripts. It automates all our build flows and make sure we always build using the same environment like most CI. As we have many applications depending on one API that have to be rebuilt every time, Jenkins provide us a cheaper alternative that is not dependent on build minutes.
Pros
- Build java applications
- Plugins for any use case
- Able to adapt to your needs
- Supports Active Directory integration
Cons
- UI can feel quite clunky and slow
- More functionality built in instead of having to rely on third party plugins
- Project of type Maven is most of the time buggy, we need to use free-style project to avoid this bugs losing out of the box functionality
Return on Investment
- Our cost for CI is really low compared if we would use cloud providers
- Cost of maintenance is a drawback, we are manually updating plugins and Jenkins on a regular basis
- We are using several different JDK versions - Jenkins let us manage this in a very good way
Usability
Alternatives Considered
Bitbucket and GitLab
Other Software Used
Azul Platform Prime, Termius