Likelihood to Recommend Mostly it is very suitable for any product based company who wants to add a CI system for their products. This tool is perfectly suitable for a company which releases builds very frequently. By using this tool they can reduce a tremendous amount of manual effort. If company's budget is not high and if they can not afford the premium plan then this tool won't be suitable for them because the basic version of this tool won't provide much functionality
Read full review Jenkins is a highly customizable CI/CD tool with excellent community support. One can use Jenkins to build and deploy monolith services to microservices with ease. It can handle multiple "builds" per agent simultaneously, but the process can be resource hungry, and you need some impressive specs server for that. With Jenkins, you can automate almost any task. Also, as it is an open source, we can save a load of money by not spending on enterprise CI/CD tools.
Read full review Pros First thing is this tool is scalable which is the biggest advantage of this tool. It won't take much time in setup and making it ready. It has a very good user interface. This tool has almost every source code repository support like Git, SVN, Microsoft Foundation Server etc. Moreover, it has very good support for various build tools like Visual Studio, MSBuild etc., which makes it even batter. We can trigger multiple builds at a time with the Premier subscription. It allows users to apply many deep levels of configurations which make the whole system even easier. Read full review Automated Builds: Jenkins is configured to monitor the version control system for new pull requests. Once a pull request is created, Jenkins automatically triggers a build process. It checks out the code, compiles it, and performs any necessary build steps specified in the configuration. Unit Testing: Jenkins runs the suite of unit tests defined for the project. These tests verify the functionality of individual components and catch any regressions or errors. If any unit tests fail, Jenkins marks the build as unsuccessful, and the developer is notified to fix the issues. Code Analysis: Jenkins integrates with code analysis tools like SonarQube or Checkstyle. It analyzes the code for quality, adherence to coding standards, and potential bugs or vulnerabilities. The results are reported back to the developer and the product review team for further inspection. Read full review Cons Mostly I don't have much more recommendation for improvement because this tool provides almost everything which would be required in any continuous integration system. But still I would suggest improvement in the reporting system. The build report is a field where they can make improvement by adding more information if they want. Read full review The UI could be slightly better, it feels kind of like the 90s, but it works well. An easier way to filter jobs other than views on the dashboard. An easier way to read the console logs when tests do fail. Read full review Usability While the day to day use is very easy, the configuration and setting up of the system or new projects can be cumbersome.
Read full review Performance No, when we integrated this with GitHub, it becomes more easy and smart to manage and control our workforce. Our distributed workforce is now streamlined to a single bucket. All of our codes and production outputs are now automatically synced with all the workers. There are many cases when our in-house team makes changes in the release, our remote workers make another release with other environment variables. So it is better to get all of the work in control.
Read full review Support Rating There is a large development community - but it is shifting as people move towards other tools. A lot of companies still use Jenkins and will build propriety tools, which doesn't help any of the open-source community. Jenkins has a lot of help and support online, but other, more modern, alternatives will have better support for newer tech.
Read full review Alternatives Considered In my previous company I have used
Jenkins for maintaining their CI system. Even this tool is also very good. The good thing about this tool is it’s an open source project. So in terms of pricing, we can consider this tool as an alternative to continua CI. One has to compare both of the products before going to use any one because both have their own benefits and drawbacks.
Read full review Overall, Jenkins is the easiest platform for someone who has no experience to come in and use effectively. We can get a junior engineer into Jenkins, give them access, and point them in the right direction with minimal hand-holding. The competing products I have used (TravisCI/
GitLab /Azure) provide other options but can obfuscate the process due to the lack of straightforward simplicity. In other areas (capability, power, customization), Jenkins keeps up with the competition and, in some areas, like customization, exceeds others.
Read full review Return on Investment Basically, this tool will reduce manual effort of creating, deploying and testing software products. So ultimately it will reduce manpower which would otherwise be required for such things. It is time saving and improves the overall performance of the entire team and system. Read full review 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 Read full review ScreenShots