Jenkins: Empowering DevOps
May 02, 2023

Jenkins: Empowering DevOps

Anonymous | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User

Overall Satisfaction with Jenkins

We are using Jenkins as CI/CD tool. We have implemented Jenkins in Kubernetes with master and worker pods. Worker pods are automatically provision and depletion base on when job is triggered. first step is trigger, Jenkins pipeline will be triggered when code is pushed in Github in particular branch. second step is to build a docker image and push it docker registry and third to apply/deploy in k8s.
  • Jenkins is highly customizable and can be extended with plugins to meet specific needs. There are thousands of plugins available in the Jenkins plugin repository that can be used to add new features or integrate with other tools.
  • Jenkins can be used to run automated tests as part of the build process. It can execute unit tests, integration tests, and other types of tests. Jenkins can also integrate with popular testing frameworks such as JUnit, Selenium, and TestNG.
  • Jenkins is well-known for its ability to perform continuous integration. It automates the process of building and testing software every time a developer commits a change to the source code repository. This ensures that the codebase remains stable and any issues are identified early in the development cycle.
  • Jenkins can be vulnerable to security issues due to its open-source nature and the availability of many third-party plugins. There have been instances where malicious plugins have been discovered, and these can pose a significant risk to organisations.
  • Jenkins can require a significant amount of maintenance, particularly when dealing with plugin updates and compatibility issues. Maintaining a stable and up-to-date Jenkins instance can be a challenge for organisations with limited resources.
  • Jenkins' reporting capabilities are limited, and it can be challenging to extract meaningful insights from the data that Jenkins provides.
  • Code Quality Analysis: Jenkins can be used to analyze code quality using various tools such as SonarQube, PMD, and Checkstyle.
  • Deployment Automation: Jenkins can be used to automate the deployment of software applications to different environments such as testing, staging, and production.
  • Continuous Delivery: Jenkins enables continuous delivery by automating the deployment process. It can automatically deploy code changes to different environments as soon as they are approved.
  • Faster Time-to-Market: Jenkins automate the build, testing, and deployment process, enabling faster feedback and continuous improvement.
  • Improved Quality: Jenkins automatically run unit tests and integration tests, ensuring that code changes meet the necessary quality standards.
  • Cost Savings: Jenkins is an open-source tool that is free to use

Do you think Jenkins delivers good value for the price?

Yes

Are you happy with Jenkins's feature set?

Yes

Did Jenkins live up to sales and marketing promises?

I wasn't involved with the selection/purchase process

Did implementation of Jenkins go as expected?

Yes

Would you buy Jenkins again?

Yes

Jenkins is well-suited for scenarios such as Continuous Integration, DevOps Automation, Agile Development, and Open-Source Software Development. It may be less appropriate for small projects, legacy systems, complex configurations, and low-resource environments. It's essential to carefully consider the specific needs of your organisation before choosing Jenkins or any other automation tool.