CASE STUDY : How Industries Using JENKINS !
what is Jenkins ?
Jenkins is an open source continuous integration tool written in Java. The project was forked from Hudson after a dispute with Oracle. Jenkins provides continuous integration services for software development.
Companies using Jenkins :
We have data on 59,079 companies that use Jenkins. The companies using Jenkins are most often found in United States and in the Computer Software industry. Jenkins is most often used by companies with 10–50 employees and 1M-10M dollars in revenue. Our data for Jenkins usage goes back as far as 5 years and 1 months.
Jenkins Market Share and Competitors in Software Development Tools :
We use the best indexing techniques combined with advanced data science to monitor the market share of over 12,500 technology products, including Software Development Tools. By scanning billions of public documents, we are able to collect deep insights on every company, with over 100 data fields per company at an average. In the Software Development Tools category, Jenkins has a market share of about 10.2%. Other major and competing products in this category include:
Top Industries that use Jenkins :
Looking at Jenkins customers by industry, we find that Computer Software (27%) and Information Technology and Services (11%) are the largest segments.
pros and cons of jenkins :
pros-
- It is free of cost.
- Easily configurable — Jenkins can be easily modified and extended. It deploys code instantly, generates test reports. Jenkins can be configured according to the requirements for continuous integrations and continuous delivery.
- Easy support — Because it is open source and widely used, there is no shortage of support from large online communities of agile teams.
- Most of the integration work is automated. Hence fewer integration issues. This saves both time and money over the lifespan of a project
cons-
- Jenkins management is generally done by a single user and that leads to tracking and accountability problems with the pushed code.
- Jenkins doesn’t allow one developer to see the commits done by another team member, readily. This makes tracking the overall release progress a rather difficult job for larger projects. This can cause a lot of trouble with the release manager.
- Jenkins doesn’t provide any analytics (there are plugins but they are not enough) on the end-to-end deployment cycle. This again goes back to the lack of overall tracking that contributes to the lack of analytics as well.
how Topdanmark in using jenkins :
Topdanmark, a leading Danish insurer chooses Jenkins as the “de facto” product to build their CI/CD platform.
Challenge:
Balancing the needs of DevOps modernization and cloud migration while maintaining legacy systems.
Solution:
A highly-configurable CI/CD platform which allows for automation and ease of development.
Results:
- 100% automatic creation of Jenkins instances
- the ability to release and deploy an artifact whenever, wherever
- software developers focused on developing software rather than operations
- smaller monoliths and containerization
Building automation with a highly-configurable Jenkins platform :
Topdanmark has two Jenkins setups. “We have two sets of systems, legacy and CI/CD,” Jon explains. “In our legacy setup, we have test, integration, release, and production environments. In our CI/CD setup, we have a non-production and a production environment.”
References :
https://www.trustradius.com/products/jenkins
thank you ! if like the article then do clap , to know more about jenkins ping me on linkedIn.