Jenkins Benefits
The deployment time has reduced considerably. Since we started using it, the solution has taken care of everything that we used to do manually. It helps us with the automation of the deployment process.
View full review »Jenkins is incredibly user-friendly, so I haven't encountered any difficulties using it. It's the only product I've used for automation, but I find it to be very intuitive and effective.
Jenkins has been instrumental in automating our build and deployment processes. We're leveraging Jenkins to automate tasks related to Telco, particularly in upgrading the manual orchestration. It's a critical tool for streamlining our operations.
Jenkins allows us to automate deployment, so I no longer have to do it manually. That's the primary use case. The other advantage of Jenkins is that it's open source. It was free for me to download and install. It's a product that's been in use for many years, so I can find a lot of support online for any issues that I may encounter while configuring anything for a given use case.
Buyer's Guide
Jenkins
March 2024
Learn what your peers think about Jenkins. Get advice and tips from experienced pros sharing their opinions. Updated: March 2024.
765,386 professionals have used our research since 2012.
Jenkins automated the build and test portion of the CI/CD pipeline.
This solution has improved our organization with how much time it saves when coding.
View full review »AS
AshutoshSharma
Software Engineer at a financial services firm with 10,001+ employees
Within the organization, we have to manage nine applications as DevOps engineers. My expertise is in Unix, so whenever they need any Unix-related help, I'm on it. Okay. For all the nine teams I have to maintain their tasks. It is up to me and I can use Jenkins, Ansible, et cetera.
View full review »MC
Mike Colarusso
Head of Infrastructure at DriveWealth Technologies
The advantage of this product is that it brought automation to the company. Instead of manually billing, manually trying to run tests, it now happens automatically.
View full review »We use Jenkins to remove human error when completing multiple deployments.
AJ
Abhilash Jain
DevOps engineer at HSBC
Jenkins has helped us to become more efficient and saves us a lot of time.
View full review »Jenkins has improved our organization by allowing us to use automatic testing to cover all the various levels of software, which includes software embedded into hardware. It has been very difficult to be able to run tests in embedded software in the past.
View full review »AK
Akanksha Kumari
Software Engineer 2 at a tech services company with 10,001+ employees
Whenever we do releases, it goes to Jenkins to publish a version of the application and the version being released. Jenkins plays a big role in this process.
View full review »KT
reviewer1483710
Software Engineering Manager at a manufacturing company with 10,001+ employees
As an organization, we have multiple products and variants. For example, a customer or OEM has multiple car lines or brands. There is a common platform, and Jenkins is helping with the source code. From this common platform, each of the variants is taken for the build. We don't need to build and test.
We get to see the results, and it is also useful to see the status in terms of success, failure, or any issue. We are able to get the status for a variant. It is connected to other dashboards such as Grafana, and we are able to see everything in one place.
It has been helpful in monitoring the progress and understanding how the daily build is happening. It gives us confidence that the products that we have built are shippable. We are able to get the status of whether a product is shippable or has a problem. This is the advantage that we have from an organizational standpoint.
View full review »BJ
Bibhu Ashis Jena
Software Engineer at a retailer with 10,001+ employees
Jenkins has helped make teams more independent. For example, if a developer wants to check if the changes they are working on have any performance impact on their application, they would typically ask the performance engineer to do load tests before and after the change. This might be difficult to accomplish every time, based on the performance engineer's bandwidth. But with help of Jenkins, the performance engineer can create a job, one time, which the developer or anyone else can run anytime, as per their requirement.
We have been able to create CI jobs for each branch of our repository. Being able to test builds for each branch before it is merged to mainstream branch helped to improve stability of the app and have faster develop-test iterations.
View full review »SB
reviewer1670496
Software Engineer at a financial services firm with 10,001+ employees
Jenkins increases our performance efficiency and saves us a significant amount of time.
View full review »SS
reviewer1727238
Software Engineer at a financial services firm with 10,001+ employees
The major benefit of using Jenkins is that it's a very secure way of deploying something to the cloud. It has also improved the drawbacks of manual deployments by making them more robust and secure, and it helps the user avoid mistakes because all the checks are there in one script which can be used every time.
View full review »FS
reviewer1748100
Cloud Security Engineer at a media company with 5,001-10,000 employees
We used to have around 30 to 40 services, which we had to use in our microservices architecture. Now, when we have to deploy things due to the same code base, we have to write the same code every time and repeatedly in the Jenkins file. It's a monotonous job, and we cannot innovate. We are just copy-pasting the Jenkins file and only changing a few things in it. That wasn't the kind of DevOps experience we want. We want some customization instead of a mundane task. But there is an option in Jenkins called Jenkins Shared Library, where we can write our own group code. Now we are using it like a programming language in the Jenkins file.
We only have to call the object and inside that object, we have to call the function or methods we want. Our Jenkins files, which were previously 309 lines were reduced to 220 or 230 lines by only calling the objects and the specific parameters. If I want Java, I will provide Java, so it is going to call the specific stage, defining my library for Java-based code. If it is NTM, it is going to call the different libraries along with the right tools for load-based applications and testing. That was a satisfying experience. As a DevOps team, we spent a lot of time creating good value in the pipeline stream instead of spending all our time copy-pasting the Jenkins file.
View full review »Rather than send emails and tickets around we can hand out "buttons" to teams so they can do self-service for actions that used to involve manual effort from the Operations group.
View full review »It provides a very user-friendly methodology to build applications. It can be very easily integrated with your repository containing the source code. It builds your applications in a user-friendly manner by just adding the repository URL.
View full review »Jenkins has greatly improved the time it takes to deliver a software package to the market.
View full review »RH
Rob Heavey
Software Developer at R.L. Heavey & Co Ltd
Jenkins has allowed for streamlined automated testing, building, and smoke testing of release candidates.
View full review »PB
PauloBorges
Senior IT Professional at Novabase
This solution provides us more effective ALM and deployment automation compared to the previous solution with Serena (now Micro Focus) Dimensions CM.
View full review »In some of my projects I had a chance to participate we used to use some commercial solutions like TeamCity or Bamboo. Since we had limited number of build machines and build agents it was really hard to organize automated acceptance and high-level system test runs as it took a while to perform the run.
Even more, since we had restricted number of build agents the huge number of long-running tests could make serious bottle-neck to the entire build process, hence, the feedback is a bit delayed. Jenkins appeared to be a good alternative to become parallel infrastructure purely dedicated for testing.
The bottle-neck problem was mitigated and we were able to make large scale runs on infinite basis. Thus, we could get results 2-3 times a day instead of 1 which brought us more consolidated and consistent picture about application under test state during the day. This trick was helpful for me on many projects
View full review »PR
reviewer1864587
Java Developer at a financial services firm with 10,001+ employees
Jenkins helps to maintain continuous integration whenever we make changes in the code and to deploy the code whenever we do any check-ins.
View full review »AK
Arwan Ahmad Khoiruddin
Software Tester at a tech vendor
We are a company run by remote workers. Using Jenkins really helps us in moving our products forward into a number of different customer segments.
View full review »Automation in general has been improved.
View full review »WA
Wasim Akram
Managing Director at Technocure
This solution has helped us in automating the build and test process, reducing time.
View full review »Jenkins has helped us in executing our test scripts without the Dev team during night time. It automatically fetches the latest build or codes and execute all your test scripts and share the report with the respective team and stakeholders.
ES
Axblade
Software Engineer at a tech services company with 11-50 employees
Most obvious: Having builds and test tasks triggered on commit helps not to break the product.
From my own experience:
We significantly reduced build times of large projects (more than 80k lines of Scala code) using build time on Jenkins as a time sample. It reduced the developer write-test-commit cycle time, and increased productivity.
Integration with GitLab reduced time used for code reviews. Jenkins posted build state and code quality reports into the merge request.
Simplified build scripts: Organisation started to integrate Pipelines as a part of a build, and built a library of common functions. It simplified and made our build scripts more readable.
Automation of chores like deployment, frequent manual tasks (like running scripts on test and production systems) reduced the time used and the number of errors made by engineers, freeing them to do meaningful work instead.
View full review »OU
Oscar Urrego
Software Test Automation Engineer at Colpatria
This solution automates the deployment process and therefore increases productivity.
View full review »We work on distribution, and are required to build and test packages frequently. Using Jenkins we have configured (generic) and automated the complete build procedure.
View full review »It improves our process because it's incorporated with the code. We don't need a UI to design the build process. It's like code for building.
View full review »CI tools such Jenkins and TeamCity, totally helps our release and tests. It saves our money, time and labour cost. And make release/delivery of the our product more visible. It drives the development team and other departments’s ambition.
View full review »It improves our release. It makes the release faster by adding an automated deploy and automation tests.
View full review »FH
reviewer1082187
Software Quality Assurance Team Lead with 11-50 employees
For test automation, Jenkins seems to be our main and central solution at the moment. We want to extend this in the future towards Jenkins pipelines, which can be very useful for having a more dynamic test infrastructure.
We've achieved continuous integration and delivery on all our commits, securing the quality of all of our products on their main branches. The features used come almost out of the box.
View full review »It's more structured, using naming conventions.
Immediate feedback on build errors, regression.
View full review »Potential deployment problems pop up almost instantly during the development process. The developers are more confident about their committed code.
View full review »This solution has provided us with better quality and less time to market for our software products. We can also automate many procedures like code review, testing, and deployment.
View full review »We used it for all continuous integration parts, like automation testing, deployment, etc.
View full review »Buyer's Guide
Jenkins
March 2024
Learn what your peers think about Jenkins. Get advice and tips from experienced pros sharing their opinions. Updated: March 2024.
765,386 professionals have used our research since 2012.