Jenkins Reviews

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.

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.

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. 

I have been using Jenkins for six to eight months. 

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

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.

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.

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

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

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

Overall, I would rate the solution a nine out of ten.

For the deployment of modules, we use Jenkins in our company.

My core work does not involve the use of Jenkins. It is something we use in the deployment process. Basically, the solution is used for interface upload and module deployment.

Improvement-wise, I would want the solution's user interface to be changed for the better. In short, the solution can be made more user-friendly.

I feel that Jenkins should make a manual or provide instructions to those planning to use the solution. Our organization has people working in the DevOps team with around ten years of experience. So, people who are fresh graduates would not know how to operate Jenkins. There was an incident in the past in which the organization deleted the production pipeline, and this was because the instructions related to the solution weren’t clear. If the instructions had been provided and the solution had a normal user interface, such an issue could have been avoided altogether.

I have used Jenkins for two and a half years. Though I am not very sure, I would say that I am using the solution's latest version. If you consider the technical side of the solution, then we are using in our company the same one being used by YouTube and Netflix.

Stability-wise, it's a pretty decent tool. Basically, It's an average product. So, I won't rate it the best or worst, as it's somewhere in the middle. If I was given to choose a better deployment service, I would definitely use that service rather than using Jenkins. I rate the solution's stability a six out of ten.

I rate the solution's scalability somewhere between seven to eight out of ten. Approximately five to ten people in my company are using Jenkins. If we plan to get more modules in our company, we will have to increase the number of employees. Currently, we don't have any plans to increase the use of the solution.

I am not aware of the available options in the market right now compared to Jenkins, but I am pretty much happy with the service that Jenkins is providing our company.

We get involved in web testing, development, and PROD for the solution's deployment process. However, I am not aware of the core setup process for Jenkins. Also, we are not involved in the pipeline readiness process, as the DevOps team does it. Therefore, I am not aware of how the initial setup was done.

Around five to ten people from the DevOps team are required to deploy and maintain the solution. Also, the deployment model for the solution is a cloud-based one. It only takes approximately five to ten minutes to deploy the solution.

In our company, we do pay for the licensing of the solution.

I would definitely recommend the solution to those planning to use it in the future. Overall, I rate the solution an eight out of ten.

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

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. 

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. 

I've been using the solution for three years. 

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.

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. 

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

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

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. 

The solution is open-source. 

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.

We are using the solution for integration purposes. We have our own DevOps pipeline. Jenkins is the key tool that is being used in the entire DevOps journey. It's like an automation build tool. It's a CI/CD: continuous integration and continuous deployment

We mostly enjoy the multi-branch pipeline support. We have multiple branches regarding, for example, the production environments. In this environment, we can use Jenkins for the deployment and integration of multiple branches.

The deploying and assessing of the development of our code and our application has been really useful. 

It's getting a bit easier for us to use Jenkins, and it is really helping us.

The solution is stable.

It can scale easily.

Jenkins is pretty flexible and integrates with many products. As of now in the market, there is no vendor dependency. They are providing a lot of plugins, so it's not very difficult to integrate with others.

If they could provide some release management and integrated security like JFrog Xray and JFrog SonarQube, that would be ideal. If they could have a built-in security assessment, like a run times security assessment, or some engine within Jenkins, that would be great. We are expecting a collaborative solution. We'd prefer not to have to go through third parties. We want everything in a single place and without having to deal with extra applications and expenses.

I would want to see if they can add some security engines or security modules within the Jenkins portal so people wouldn't have to buy or go for some other outside products. As of now, security is the biggest concern. That should be the first priority after any technology.

They need to improve their documentation. When you compare it to Red Hat documentation which is very nice, you find that Jenkins does not provide much helpful documentation.

The product needs to showcase more use cases. 

I've used the solution for eight to ten years.

The stability is good. it's reliable. I'd rate the stability four out of five. 

The solution can scale quite well. 

We only have 20 to 30 users on the product right now. It's something our development team uses daily.

The other people handle support cases. I'm not quite sure how quickly they respond since we have different infra teams, so they handle all these cases.

The only competitor to Jenkins is Argo CD for Jenkins. We are not using it yet.

The approach is now changing to GitOps. People are moving towards the GitOps rather than the old DevOps model. That's where the Argo CD or Flex comes in as alternative tools that are picking up interest in the market.

It would be easier to set up the solution if they offered better documentation. With more direction, it would be easier to deploy the solution. The steps shown in the documentation are not very clear. 

It shouldn't be like a puzzle. I have to search everywhere, every time, and Google what I need. Rather than going to blogs and some open-source community blogs, it's better to have its own documentation. It should be very straightforward and clearly show the steps, the minimum requirements, and the bottlenecks. It should all be centralized as well.

I'd rate the setup process a three out of five in terms of ease of implementation.

I'm not sure of the exact pricing of the product. My understanding is that it is not very expensive. It's an open-source tool. They do also have an enterprise version, which is what we use. It's the same tool whichever you use, however, with enterprise, you get support.

We are customers of Jenkins.

I'd rate the solution seven out of ten.

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

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. 

I have used Jenkins for five or six years.

Jenkins is highly stable. 

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

The documentation is extensive and community support is excellent.

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. 

We deployed Jenkins in-house.

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

I mainly use Jenkins to create automatic triggers for pushing code.

Jenkins' most valuable feature is Pipeline.

Jenkins takes a long time to create archive files.

Jenkins' stability is good, and we haven't had any issues with downtime.

Jenkins is scalable in the sense that we can develop as many jobs as necessary. 

Jenkins' technical support team is small but helpful.

Positive

The initial setup isn't very complex, though it may take some time to create end scripts because it lies in the backend and needs to work during free integration time.

We used a uDeploy IBM product and team.

I would rate Jenkins eight out of ten.

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. 

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.

I have been using Jenkins for approximately three years.

Jenkins is stable.

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. 

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.

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.

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.

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

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.

We have multiple job templates available. You just need to find the best template for your needs. If you just want to do a Maven build, there will be a more suitable template there. For something else, if you just have one rebuild and you want to deploy it from the server, there will be some other job template available. We have multiple job templates, so we need to configure according to that template and then it's okay.

The solution is deployed on-premises. About 15% of my organization is using this solution. It's basically used by the DevOps engineers. Not all the developers use it.

With Jenkins, the pipeline will take your code from any versioning system like GitHub or Bitbucket. All the security scans can happen in one go and then all the tests also get run. You can just build one container in it and deploy it.

For this solution to be a 10, it has to be a lot more stable. Maybe the public version of Jenkins is stable, but in our case it's not stable. There is a knowledge record, but you still need to figure out the way to configure it initially. It has to be easier. There should be some indication that an error is not caused by Jenkins.

I have been using this solution for a year and a half.

Because we are using in-house tools, it's a little bit unstable.

It's very scalable.

We haven't needed to call support. If we have any issues, we contact HSBC's support team or the one who created the template.

Initial setup is difficult. From start to finish, deployment takes an hour and a half.

We are using in-house tools.

Jenkins is open-source.

I would rate this solution 6 out of 10. 

I have less knowledge of the raw Jenkins, but Jenkins is doing almost all the stuff that I want it to do, but it's not a 10 because of the difficulties to configure it, to make it work, to do end-to-end, and then the stability.

You should first find out all the requirements that Jenkins is doing. You need to find out if you have any coding issue or if Jenkins has any issue. Now I train people to use it, and normally these are the issues that I find. There are many occasions where there is an issue with code but it's not always that Jenkins is wrong; sometimes it's the code that is breaking.