Try our new research platform with insights from 80,000+ expert users
Software Engineer 2 at a tech services company with 10,001+ employees
Real User
Links well to a repository and is stable and scalable
Pros and Cons
  • "GitHub linking is pretty good. We have a deployment application where we can run our tests and add various variables to be passed as assertions to those tests. This is pretty fluid with Jenkins."
  • "Sometimes, random errors of metadata are not there, which causes delays. These are essentially gaps in the information being passed to the job."

What is our primary use case?

The primary use cases include manifest generation and publishing modules.

How has it helped my organization?

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.

What is most valuable?

GitHub linking is pretty good. We have a deployment application where we can run our tests and add various variables to be passed as assertions to those tests. This is pretty fluid with Jenkins.

It is a stable solution and is generally scalable.

What needs improvement?

Sometimes, random errors of metadata are not there, which causes delays. These are essentially gaps in the information being passed to the job. This could be reduced and would save a lot of time.

Jenkins runs in correlation with GitHub but can only run one job at a time. Also, that job is a pre-selected job. So, if you select a particular job, then that job would run for all your pull requests. It would be amazing if for pull request one, for example, I could do build one, and for pull request two, I could do build two.

Buyer's Guide
Jenkins
October 2024
Learn what your peers think about Jenkins. Get advice and tips from experienced pros sharing their opinions. Updated: October 2024.
814,649 professionals have used our research since 2012.

For how long have I used the solution?

I've been working with Jenkins for two years.

What do I think about the stability of the solution?

It's quite stable and pretty reliable.

What do I think about the scalability of the solution?

To a large extent, it is scalable; after that, some manual interference is required at certain points.

In our company, everybody works with Jenkins, so we have more than 10,000-20,000 users.

How are customer service and support?

I am satisfied with the technical support services.

What other advice do I have?

I would recommend Jenkins and would rate it at nine on a scale from one to ten.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
it specialist at a tech services company with 10,001+ employees
Real User
Top 5
Customizable plugins enhance integration for build and deployment automation
Pros and Cons
  • "Also, the ability to customize these plugins is valuable. Its user-friendliness stands out, especially in its user interface which allows easy installation and configuration."
  • "Jenkins could improve in areas related to Kubernetes and Docker container integration, like machine allocation of nodes and Marshaling integration improvements."

What is our primary use case?

We used Jenkins for integration purposes, primarily for integrating with version control systems like Git and build tools such as Maven. Later, there were plans to use it in Docker deployment for Docker containers. 

I configured environments for non-production, production, and development in the pipeline. 

I also used Jenkins for a Bluegreen deployment strategy, quality assurance with SonarQube, and artifact storage in JFrog Artifactory.

How has it helped my organization?

In our previous company, Jenkins was used for complete automation of build and deployment in a project. From part of automation and customization, I was involved in the project.

What is most valuable?

The most valuable feature of Jenkins is the plugins available. You name any tool, and there is a plugin available for it in Jenkins. 

Also, the ability to customize these plugins is valuable. Its user-friendliness stands out, especially in its user interface which allows easy installation and configuration.

What needs improvement?

Jenkins could improve in areas related to Kubernetes and Docker container integration, like machine allocation of nodes and Marshaling integration improvements. Making these aspects more robust would be beneficial.

For how long have I used the solution?

I have been using Jenkins for around five years now.

What do I think about the stability of the solution?

Jenkins is stable. Any tool can have latency of a few seconds, but I would rate Jenkins four and a half out of five for its stability.

What do I think about the scalability of the solution?

Jenkins is not as scalable compared to container solutions like Docker or Kubernetes. While it can be configured at the server end, the other solutions offer more robust automation and scalability.

How are customer service and support?

My team handles technical support for Jenkins when necessary. However, since I moved into AI and machine learning projects, I haven't been closely involved with technical support issues.

How would you rate customer service and support?

Positive

How was the initial setup?

The initial setup of Jenkins is very straightforward and not difficult.

What was our ROI?

By installing Jenkins in a master-slave environment, there is significant cost saving, making it a cost-effective tool compared to other CI tools.

What's my experience with pricing, setup cost, and licensing?

I do not have extensive knowledge on the pricing or licensing aspect as I used Jenkins for free at the local machine level. However, it is generally regarded as cost-effective.

What other advice do I have?

I would rate it a nine out of ten.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
PeerSpot user
Buyer's Guide
Jenkins
October 2024
Learn what your peers think about Jenkins. Get advice and tips from experienced pros sharing their opinions. Updated: October 2024.
814,649 professionals have used our research since 2012.
PeerSpot user
Software Engineer at a retailer with 10,001+ employees
Real User
Facilitates Continuous Integration with almost any systems used for app development
Pros and Cons
  • "Continuous Integration. Jenkins can integrate with almost any systems used for application development and testing, with its plugins."
  • "Upgrading and maintaining plugins can be painful, as sometimes upgrading a plugin can break functionality of another plugin that a job is dependent on."

What is most valuable?

  • Continuous Integration. Jenkins can integrate with almost any systems used for application development and testing, with its plugins. 
  • It is open source and can be hosted on-premise. 
  • Because of its wide usage and support forums, one can easily find solutions to any issues they might face.

How has it helped my organization?

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.

What needs improvement?

Upgrading and maintaining plugins can be painful, as sometimes upgrading a plugin can break functionality of another plugin that a job is dependent on.

For how long have I used the solution?

One to three years.

What do I think about the stability of the solution?

No issues.

What do I think about the scalability of the solution?

No issues.

How are customer service and technical support?

Excellent.

Which solution did I use previously and why did I switch?

No previous solution.

How was the initial setup?

The initial setup is straightforward. It can be easily downloaded and installed from the Jenkins website. New plugins can also be added easily, based on the requirement.

What's my experience with pricing, setup cost, and licensing?

Jenkins is open source.

Which other solutions did I evaluate?

We explored other open source CI tools like Travis CI and CircleCI.

What other advice do I have?

Jenkins is a great tool for continuous integration. It has a wide variety of plugins to support anything from development to automation, performance testing, security testing, and many more. It also has the best support and documentation. If one is ready to spend dedicated resources on proper access control and plugin management, Jenkins can easily be the tool of choice for CI.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Devi Vara Prasad Dommeti - PeerSpot reviewer
Senior Engeener at a consultancy with 51-200 employees
Real User
Effective open source design, stable, and helpful online support available
Pros and Cons
  • "The most valuable feature of Jenkins is its open source."
  • "The disadvantage of Jenkins is writing Groovy scripts. There are other CI tools where you do not need to write this many scripts to manage and deploy."

What is our primary use case?

We're deploying our pipeline through CI/CD with both engines, most use it for CI purposes only. We are building our CAR files and deploying them in the endpoint cluster, such as Kubernetes as well as on-premise systems. We are using the management where I can write playbooks and deploy them. I call the playbook through the Jenkins Groovy script. We can do multiple instances, at a single time. 

What is most valuable?

The most valuable feature of Jenkins is its open source.

What needs improvement?

The disadvantage of Jenkins is writing Groovy scripts. There are other CI tools where you do not need to write this many scripts to manage and deploy.

For how long have I used the solution?

I have been using Jenkins for approximately three years.

What do I think about the stability of the solution?

Jenkins is stable.

What do I think about the scalability of the solution?

The scalability is easy in Jenkins because we are using a master and worker node architecture.

We have many departments using this solution in my company, such as DevOps and Automation teams. 

How are customer service and support?

The technical support was never used. We followed the standard documents. I never interacted with Jenkins technical because there is a wide user base online. Jenkins has been a long time in the market, we easily find help if needed. Similarly, how Python codes are molded and a lot of companies are using it. You can easily find a solution if you're stuck.

How was the initial setup?

Jenkins is easy to set up. The full deployment can take some time if there is a lot of data to be accessed. There are the data analysis files, and queries, and we need to update everything in the end systems, such as a center DB. This can take some time, approximately half an hour due to the large file size. The majority of things can be deployed within five to seven minutes.

What was our ROI?

There is a cost saving by using Jenkins because instead, we do not have to depend on the public cloud or any private cloud CI tools.

What's my experience with pricing, setup cost, and licensing?

We are using the free version of Jenkins. There are no costs or licensing.

What other advice do I have?

I advise others that want to try Jenkins to first test it locally and then they can integrate it with the cloud. Whoever wants to use the continuous integration tools, should first go with Jenkins and then, later on, they can try other market available tools.

I rate Jenkins a nine out of ten.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Rajeshkumar Gone - PeerSpot reviewer
Senior Software Engineer at Aviso AI
Real User
A good web development solution that lacks in mobile development functionality
Pros and Cons
  • "We really appreciate that this solution is plug and play. When coding in the version control system, this product completes the build process automatically."
  • "We would like to see the addition of mobile simulators support to this solution, as part of its open-source offering. We currently have to carry out manual testing for these platforms."

What is our primary use case?

We use this solution to build, test, and then deploy new software to the FTP server.

How has it helped my organization?

This solution has improved our organization with how much time it saves when coding.

What is most valuable?

We really appreciate that this solution is plug and play. When coding in the version control system, this product completes the build process automatically.

What needs improvement?

We would like to see the addition of mobile simulators support to this solution, as part of its open-source offering. We currently have to carry out manual testing for these platforms.

For how long have I used the solution?

We have worked with this solution for around four years.

What do I think about the stability of the solution?

We have found the stability of this solution to be good.

What do I think about the scalability of the solution?

Due to the lack of mobile simulators, we have not scaled this solution.

How are customer service and support?

We have not had to contact the technical support team; the official documentation provided has resolved any issues we came across.

How was the initial setup?

We found the initial setup of this solution to be okay. The setup isn't complicated, but there is some step by step documentation provided that will need to be read and followed during the process.

The deployment of the product took one or two days initially, and only took one person to action.

What about the implementation team?

We carried out implementation and deployment of this product using our in-house team.

What's my experience with pricing, setup cost, and licensing?

This is an open-source solution for the basic features. However, if an organization wishes to include specific functionality, outside of the basic package, there are extra costs involved.

Which other solutions did I evaluate?

We previously trialed an AWS-based product. However, it was complex to use and conflicted with some of our existing software.

What other advice do I have?

We highly recommend this solution for web development. However, for mobile development, it may be better for organizations to consider other options.

I would rate this solution a five out of ten.

Which deployment model are you using for this solution?

Public Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
PeerSpot user
Senior iOS Developer at a media company with 5,001-10,000 employees
Real User
​This is a very good, powerful and flexible product, but requires a lot of time investment to get the maximum out of it.

What is most valuable?

The Jenkins Job DSL plug-in is the most valuable.

How has it helped my organization?

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.

What needs improvement?

The installation process could be simplified, especially on Mac OS X.

For how long have I used the solution?

I've used it for eight months.

What was my experience with deployment of the solution?

Yes because the installation process is not obvious.

What do I think about the stability of the solution?

The default settings do not work properly on Mac OS X. You have to tweak JVM parameters and allocate more heap memory as well as change other parameters to have a stable Jenkins server.

What do I think about the scalability of the solution?

I haven't had to scale up yet. We have one build box which is running two agents on it.

How are customer service and technical support?

Customer Service:

As this is open source, there is no such thing as customer service, but there is a big community to look for information and get answers.

Technical Support:

As this is open source, there is no such thing as tech support, but there is a big community to look for information and get answers.

Which solution did I use previously and why did I switch?

Personally, I previously used Bamboo. I switched because I changed jobs and at my new place Jenkins had been used. It would unjustified to do a move from Jenkins to Bamboo, given that Jenkins is capable of performing same tasks.

How was the initial setup?

It was complex and additional knowledge about launch agents and daemons is required. There are at least three, if not four, different ways to install and configure Jenkins, which is not always good.

What about the implementation team?

We implemented it in-house.

What was our ROI?

It's high because the product is free.

What's my experience with pricing, setup cost, and licensing?

The original setup. for us, was the cost of a new Mac Mini box which costs, from $1,000 to $2,000 depending on the configuration.

What other advice do I have?

This is a very good, powerful and flexible product, but requires a lot of time investment to get the maximum out of it.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
it_user217035 - PeerSpot reviewer
it_user217035Senior iOS Developer at a media company with 5,001-10,000 employees
Real User

mgrebenets.github.io
It's very subjective, just the way a blog post should be :)

See all 4 comments
AnkurGupta9 - PeerSpot reviewer
Principal DevOps Engineer at Guavus
Real User
Top 10
There is a large user base to provide community support, which I find very valuable.
Pros and Cons
  • "Jenkins is the most widely used development tool, so there are many plugins and it's easy to integrate. There is a large user base to provide community support, which I find very valuable. If I need to find a better way to do something, I can always get help from the community. Automation is about thinking outside of the box, and other users are constantly adding new plugins."
  • "I would like them to provide space for people to have a central node that stores all the logs of workspace information in a distributed fashion to facilitate backup and restoration. Currently, everything is stored on one node, so you need to set up distributed storage or an endpoint that you can use for backing up your information."

What is our primary use case?

We use Jenkins for CI/CD application. It helps us develop and push out applications. 

What is most valuable?

Jenkins is the most widely used development tool, so there are many plugins and it's easy to integrate. There is a large user base to provide community support, which I find very valuable. If I need to find a better way to do something, I can always get help from the community. Automation is about thinking outside of the box, and other users are constantly adding new plugins.

What needs improvement?

I would like them to provide space for people to have a central node that stores all the logs of workspace information in a distributed fashion to facilitate backup and restoration. Currently, everything is stored on one node, so you need to set up distributed storage or an endpoint that you can use for backing up your information. 

For how long have I used the solution?

I have used Jenkins for five or six years.

What do I think about the stability of the solution?

Jenkins is highly stable. 

What do I think about the scalability of the solution?

Jenkins can scale up. We have about 100-150 users working with it now. 

How are customer service and support?

The documentation is extensive and community support is excellent.

How was the initial setup?

I rate Jenkins eight out of 10 for ease of setup. Jenkins evolved from running on a virtual machine to deploying inside Kubernetes, which has simplified the setup. Running Jenkins inside Kubernetes is straightforward. The only challenge is configuring the backup. We have two people maintaining Jenkins by updating the plugins and server about once every other month. 

What about the implementation team?

We deployed Jenkins in-house.

What's my experience with pricing, setup cost, and licensing?

Jenkins is an open-source product, but you have the option to buy an enterprise license.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Yantao Zhao - PeerSpot reviewer
Software Integration Engineer at Thales
Real User
Top 5
Great price point, most popular automation in the world, with excellent task planning options.
Pros and Cons
  • "Jenkins has excellent task planning features."
  • "Partition security for the workflow of projects is not yet an option."

What is our primary use case?

We use Jenkins for integrated reporting. We have different projects that require coaching, gate configuration, and clone effects. We build packages, deploy, and upload-pack eights. We start at software changes and follow the process through to final testing and eventually launching. 

What is most valuable?

Jenkins has excellent task planning features. 

What needs improvement?

We have a variety of examples in our organization.  We have security configurations that we would like to isolate across our platform. It is not always easy to control the permissions for each user. There are cases where I do not want everyone to have access to the technical aspect of a job or even that the job exists.

For how long have I used the solution?

I have been using Jenkins now for ten years.

What do I think about the stability of the solution?

We have found Jenkins to be very stable.

What do I think about the scalability of the solution?

I believe Jenkins is scalable. We have over two hundred users. We have plans to increase this number.

How are customer service and support?

We have not used technical support. We just Google, from the internet. Most of the time we can solve it on our side.

How was the initial setup?

The initial set-up is easy for a single-link system. For more complicated systems it is not easy. As a product, Jenkins has been in the top five for more than five years, so that is not a problem.  

What about the implementation team?

We did an in-house implementation. We have an incremental process for deployment. We also have a complete patent for official patent deployment. We have two patents, one for development and one for official relief. We have an integration team that is responsible for these patents.

What's my experience with pricing, setup cost, and licensing?

Jenkins has a free licensing program.

What other advice do I have?

Jenkins is the most popular automation engine in the world. There are other options, but fewer users. There are some other choices in the market but Jenkins is definitely number one. I would rate Jenkins an eight out of ten.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user