Jiurui Zhang - PeerSpot reviewer
Senior Quality Engineer, Cloud Platform Engineer at Belong
Real User
Top 20
A free tool that has broad community support
Pros and Cons
  • "The deployment of traditional Jenkins is easy."
  • "Jenkins is an old product, and we encounter performance issues and slow response. Also, some of the plugins are not stable."

What needs improvement?

Jenkins is an old product, and we encounter performance issues and slow response. Also, some of the plugins are not stable. 

For how long have I used the solution?

I have been working with the product for eight years. 

What do I think about the stability of the solution?

I rate Jenkins' stability a six out of ten. 

What do I think about the scalability of the solution?

I rate the product's scalability an eight out of ten. My company has 150 users for Jenkins. 

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.

How was the initial setup?

The deployment of traditional Jenkins is easy. I rate cloud-based deployment a five out of ten. It takes half and hour to complete. 

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

We use the tool's free version. 

What other advice do I have?

Jenkins has broad community support. I rate it a nine out of ten. 

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
PeerSpot user
Amiya Acharya - PeerSpot reviewer
Senior Automation Engineer at a tech vendor with 10,001+ employees
Real User
Top 5Leaderboard
Easy to learn, straightforward to set up, and has good documentation
Pros and Cons
  • "It's very easy to learn."
  • "We need more licensed product integrations."

What is our primary use case?

We primarily use the solution for CI, continuous integration, and as a content server. 

What is most valuable?

The solution is quite scalable and user-friendly. It's very easy to learn. 

The initial setup is straightforward. 

It's stable.

The solution can scale.

It has good documentation to help with troubleshooting. 

What needs improvement?

The solution needs more support for different Docker setups. Right now, it's a bit complicated. If there were better Docker integration, it would be ideal. Right now, there is no easy plug-in. You really have to explore it a bit more to figure out how to do it. 

We need more licensed product integrations. For example, having a licensed integration with Jira would be great.

It is a bit limited in terms of its vision right now. 

For how long have I used the solution?

I've been using the solution for three years. 

What do I think about the stability of the solution?

The solution is stable. Sometimes the host server may be down. However, most of the time, it's stable. 

I'd rate the stability nine out of ten.

What do I think about the scalability of the solution?

It's a pretty scalable solution. We find it easy to expand. 

We're using it for a large application and haven't had any issues. It's a bit close sometimes; however, it doesn't crash at regular intervals. Sometimes there might be some server down or something that might cause an issue.

I'd rate the scalability nine out of ten. 

We have about 300 or more people using the solution. We tend to use the product on a weekly basis. 

How are customer service and support?

It is an open-source solution and has good documentation. 

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

I've also used Bamboo, which is a bit more user-friendly. It has good integrations and licensing.

How was the initial setup?

The solution offers a very straightforward setup. If you have a little bit of technical knowledge, it shouldn't give you any trouble. I'd rate the ease of setup nine out of ten. 

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

The solution is open-source. 

What other advice do I have?

We're a partner.

Before using the solution, it is helpful to have some Git or CI/CD experience under your belt. It would help with context when starting to use Jenkins. 

I'd rate the solution eight out of ten.

Which deployment model are you using for this solution?

Public Cloud
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
PeerSpot user
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.
Snr Tech Engineer at a transportation company with 10,001+ employees
Real User
Provides a single-pane-of-glass view, but error messages need improvement
Pros and Cons
  • "When we have manual tasks, we have to depend on multiple technical teams. With Jenkins, we can bring all the technologies together by the click of a button. We can see results without having to depend on different teams. Jenkins makes life easy for the database and DevOps teams."
  • "Tasks such as deployment, cloning, database switchover, and all other database missions and tasks are being done through Jenkins. If a job does not go through, at times the error message does not clearly indicate what caused the failure. I have to escalate it to the Jenkins DevOps team just to see what caused the failure. If the error message is clear, then I wouldn't have to escalate the issue to different teams."

What is our primary use case?

We use Jenkins for database products and automation of other applications as well.

What is most valuable?

When we have manual tasks, we have to depend on multiple technical teams. With Jenkins, we can bring all the technologies together by the click of a button. We can see results without having to depend on different teams. Jenkins makes life easy for the database and DevOps teams.

What needs improvement?

Tasks such as deployment, cloning, database switchover, and all other database missions and tasks are being done through Jenkins. If a job does not go through, at times the error message does not clearly indicate what caused the failure. I have to escalate it to the Jenkins DevOps team just to see what caused the failure. If the error message is clear, then I wouldn't have to escalate the issue to different teams.

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?

On a scale from one to ten, I would rate Jenkin's stability at three.

What do I think about the scalability of the solution?

It is scalable because the Jenkins jobs are in AWS, whereas the deployments are being done on-premises. My understanding is that these will be brought on-premises as well.

We have 10 plus users for the database and application teams. We have less than 50 databases.

What other advice do I have?

If you want to have a single-pane-of-glass view in terms of automation, you can go for Jenkins. It does the job it's supposed to do. Therefore, I would give this solution a rating of seven out of ten.

Which deployment model are you using for this solution?

On-premises
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
PeerSpot user
Devi Vara Prasad Dommeti - PeerSpot reviewer
Senior Engeener at a consultancy with 51-200 employees
Real User
Top 5
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
Ullas Soman - PeerSpot reviewer
DevOps Consultant at Coforge Growth Agency
Real User
Top 5
An open source automation server with a useful business logs feature
Pros and Cons
  • "I like the business logs. It's a very useful tool. Client-server communication is also very fast."
  • "It would be better if there were an option to remove its Java dependency. This would make it more compatible with other software, and it could be much better. At present, we have to depend on Java whenever we want to deploy agents."

What is our primary use case?

We use Jenkins for the continuous integration of our jobs and products. We do have a couple of jobs that were created through Jenkins, and it's logical to start like that, as it requires the Java framework to run on Jenkins. We have the developer code; we begin with the power and the PSQL. 

What is most valuable?

I like the business logs. It's a very useful tool. Client-server communication is also very fast.

What needs improvement?

It would be better if there were an option to remove its Java dependency. This would make it more compatible with other software, and it could be much better. At present, we have to depend on Java whenever we want to deploy agents.

For how long have I used the solution?

I have been using Jenkins for about two years.

What do I think about the stability of the solution?

Jenkins is a stable product.

What do I think about the scalability of the solution?

Jenkins is a scalable product. 

How was the initial setup?

The initial setup is straightforward.

What other advice do I have?

I would tell potential users that Jenkins is a very good tool, which I highly recommend. It's very helpful for the continuous integration of any products. For example, if you want to dial up some things on production and want to go live, we can continuously integrate them. We can put it onto the report starting from the no-code and the subsequent environment and letters. So, Jenkins is very highly recommended.

On a scale from one to ten, I would give Jenkins a ten.

Which deployment model are you using for this solution?

Public Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Amazon Web Services (AWS)
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Software Engineer at a financial services firm with 10,001+ employees
Real User
Easy to use with clear documentation and good dashboards
Pros and Cons
  • "The initial setup is simple."
  • "We cannot change the ownership of any directory or file or any kind of directory."

What is our primary use case?

We primarily use the solution as a build automation tool.

If we have to do some automation, we have to deploy the code on a server, and on the production server, so we can create a Jenkins pipeline, which we can call from Jenkins itself. Therefore, whenever we want to deploy the code on a server, on the production server, we use the Jenkins pipeline.

How has it helped my organization?

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. 

What is most valuable?

From a deployment perspective, we don't require any passwords or any permissions and all. Everything we can do from Jenkins.

Whenever something fails, so we have the facility to check the logs. Based on that, we can find the solutions and we can fix things.

The initial setup is simple.

The stability of Jenkins is good.

The dashboards are very good.

The solution has been very easy to use.

We have found that the solution offers very good, very clear documentation. Everything is laid out well and easy to explain to a new user.

What needs improvement?

There are some 13 commands that we cannot run for Jenkins. For those particular commands, for the smallest small command (not the bigger task at a deeper level), for example, a copy command, we cannot run it from Jenkins. We cannot change the ownership of any directory or file or any kind of directory. In that case, we have a dependency on, for example, Ansible. There are some limited commands in Jenkins. 

For how long have I used the solution?

I joined this current organization in November of 2019. From November 2019 onwards, I've been using this. It's been approximately two years at this point.

What do I think about the stability of the solution?

The solution has been very stable. There are no bugs or glitches. it doesn't crash or freeze. 

In some cases, it is a very reliable solution and tool. We had some dependencies, however, we have another solution for those dependencies. Whenever we do not have any dependencies somewhere else, we can use Jenkins.

What do I think about the scalability of the solution?

I've never attempted to scale Jenkins.

My team has nine applications. Our organization has between 250 to 300 people. Many people are using the product. I'm not sure how many teams we have, however, I am sure that all the teams are using Jenkins.

How are customer service and technical support?

I don't directly deal with technical support. Typically, I create a ticket, however, usually,  I try troubleshooting from my end. If the issue is not from our end, we have to raise a GR ticket and it takes approximately 24 to 48 hours to get it resolved, or for them to actually get in touch with us. 

In my company, we also have a Sharepoint that contains troubleshooting documentation that is quite helpful.

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

I was previously using Ansible.

How was the initial setup?

The solution offers easy deployment. We just need to follow some steps and we have to give some URL paths and that's all. It's not time-consuming.

Initially, we do the setup for a particular or one particular task. If whenever we get a request in the future and based on the task, we just make a copy of that initial task and we do the minor changes and in that way, we can implement new tasks very easily.

We have a Jenkins central team. Whenever they upgrade, they send us a notification. A separate team handles the upgrade.

What about the implementation team?

We are able to implement the solution for our clients.

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

I understand that the licensing is renewed about once a year. The pricing itself is fine. I wouldn't describe it as being overly expensive.

What other advice do I have?

I'm not sure which version of the solution I'm using.

I'm just using this tool to automate items for my teams. Whenever my team requires my help, I support them.

I would recommend the solution to other users and organizations, however, it depends on the requirement and what exactly the users need. 

I'd rate the solution at a nine out of ten.

Which deployment model are you using for this solution?

Private Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Other
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Head of Infrastructure at DriveWealth Technologies
Real User
A great open community; has enabled our company to move to full automation
Pros and Cons
  • "Has enabled full automation of the company."
  • "Some kind of SaaS product would be helpful in providing organizational structure."

What is our primary use case?

This solution is open source and we use it for the entire bill pipeline - for building different languages, for running reports on code coverage, running our QA tests, automated tests, and for deployment. We are customers of Jenkins and I'm head of infrastructure. 

How has it helped my organization?

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. 

What is most valuable?

The best thing about Jenkins is that it's such an open community, and it has a bazillion plugins which is a neat feature. Anything you want to do, someone else has probably already done it.

What needs improvement?

Despite there being a whole lot of community input on the solution, nobody is providing professional services around it. Jenkins itself is a very small company but it would be great if they could host and offer some kind of SaaS product which would provide an organizational structure of some sort.

For how long have I used the solution?

I've been using this solution for 13 years. 

What do I think about the stability of the solution?

Stability is not top notch but it's pretty good. 

What do I think about the scalability of the solution?

The solution is very scalable, I probably have around 60 people using it, mainly developers checking whether there are any errors. We have around 10, 15 QA people, power users, and  another 40, 45 developers looking at it. The solution is being extensively used but we only need one person to deal with maintenance. 

How was the initial setup?

The initial setup was straightforward and didn't take too long, maybe a few days. Implementation was carried out in-house.

What other advice do I have?

It's important to take the time to research the solution and find what's right for you. Since it's so customizable, there's a million ways to do things and since there's no professional services that says this is the right way, you have to figure it out on your own. Take that time, do the research, try things out. Make sure it works before you go ahead and put it into your whole organization. This solution touches the bases of everything we need to do. Professional services aren't there, but that's the only downside. Other than that, we're very happy with the product. 

I rate this solution a nine out of 10. 

Which deployment model are you using for this solution?

Public Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Amazon Web Services (AWS)
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Senior Software Tester at SMARTe Inc
Real User
Top 20
Efficient for Pipelines, easy to deploy and reliable solution
Pros and Cons
  • "Jenkins is very user-friendly."
  • "Performance-wise. This needs to be improved. Not only performance-wise, some functionality or some features can be added to Jenkins."

What is our primary use case?

We're using Jenkins for projects. We just need to run Jenkins pipelines and stuff.

We use iPlus for web application testing automation. Multiple people can work on the same piece of code. Once we push the code to the Git repositories, by default, we need to check if it's working and if the code passes the tests. 

If any tests fail, we need to verify the logs in Jenkins. So, those are the main things we do with Jenkins.

What is most valuable?

Pipelines are the most valuable feature. We mostly work on pipelines; it's only because we have to verify the nightly build sign to see whether it is correctly done or not. So, for that kind of function, we usually work on the technical side.

What needs improvement?

Performance-wise. This needs to be improved. Not only performance-wise, some functionality or some features can be added to Jenkins. 

Suppose we used to get a notification for part or field test cases. So that can also be improved on the technical side. We can get a notification through email or Slack channel or Teams channel. So that kind of notification also, they can also be improved on the technical side. 

For how long have I used the solution?

I have been using Jenkins for six to eight months. 

What do I think about the stability of the solution?

I would rate the stability a ten out of ten. I didn't face any crashes. It is hundred percent stable. 

What do I think about the scalability of the solution?

I would rate the scalability a nine out of ten. We have multiple vendors, so we care. We are also one of the vendors for this project. 

So in our project, we are using almost 20 to 25 members using Jenkins.

How was the initial setup?

I would rate my experience with the initial setup a nine out of ten, where one is difficult, and ten is easy.

Jenkins is very user-friendly.  

The time taken for deployment depends on the performance of the engine. Sometimes, it may be slow. Usually, we won't face a performance issue. So, within a fraction of a second or within a fraction of a minute, the deployment can be done.

The deployment depends upon the code. If it is a small piece of code or it's a large piece of code. So it depends on the code.

What about the implementation team?

We have a separate DevOps team for maintenance and other tasks.

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

This is not open source. It's price-based, for example, premium-based.  

What other advice do I have?

Stability-wise, reliability-wise, and performance-wise, it is a good tool. 

Overall, I would rate the solution a nine 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.
Flag as inappropriate
PeerSpot user