What advice do you have for others considering Jenkins?

I would give Jenkins a rating of nine on a scale from one to ten.

Based on my experience, I would recommend Jenkins since it greatly automates processes, securely stores sensitive information, supports multiple integrations, and maintains deployment history effectively. I'd rate the solution seven out of ten.

I would not recommend Jenkins if you want to get your product to market quickly. It requires experience and a clear understanding of your requirements. For faster go-to-market solutions, cloud-based alternatives like CircleCI might be better.

If someone asked me which CI/CD tool I recommend, I would suggest GitLab. However, if someone must choose between Jenkins and Tekton, I recommend Jenkins. I rate the product a six out of ten.

I highly recommend this product because I believe it's excellent. It's versatile enough for users to adapt it to their specific needs easily. I find it incredibly helpful and straightforward to use. Overall, I would rate it nine out of ten.

Jenkins is deployed on the cloud in our organization. The solution is installed in our AWS server. The solution is widely used to build, develop, and automate projects. The solution facilitates continuous integration and continuous delivery by automating the building, testing, and deployment of code change. We update Jenkins plug-ins, configure Jenkins with JVM, and always review and optimize our job configurations. You can consider using a cloud-based scaling solution to add or remove builds dynamically based on demand. Platforms like AWS EC2 and Kubernetes can be integrated with Jenkins. Overall, I rate the solution ten out of ten.

Stability-wise, reliability-wise, and performance-wise, it is a good tool. Overall, I would rate the solution a nine out of ten.

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

I would definitely recommend using this solution. Overall, I would rate the solution a six out of ten because Jenkins is a very useful tool. However, it's not a ten because it has some issues like too many features cramped in the UI, and users need to invest some time in educating themselves to fully understand it.

I would rate Jenkins a nine out of ten.

People must consider the solution for enterprise support if they find it easy to read the documentation. If an organization has a good number of people for maintenance, they can choose the product. Overall, I rate the tool an eight out of ten.

Jenkins is Java-based. Our organization recently upgraded to Jenkins 2.390. We deploy Jenkins into VMware vCenter machines. We use Amazon Web Services for pipeline automation on the cloud. I would recommend Jenkins to others. Jenkins is a popular CI/CD tool commonly used by DevOps teams. I rate Jenkins an eight out of ten.

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'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.

Overall, I would rate Jenkins a seven out of ten.

I rate Jenkins two out of 10. If you think it's going to save you money because it's open source, think again. Find an alternative, such as GitHub Actions or GitLab.

My advice to others is this is a tool that will help save time have good coverage for the validation environment and test more hardware capabilities. For example, it can handle an embedded system and it can run any type of script. I rate Jenkins a nine out of ten.

There might be unnecessary overheads if you're trying to use Jenkins for very simple deployments. I would say make sure that you actually need to use Jenkins for specific actions. I would rate this solution a ten out of ten.

We are customers of Jenkins. I'd rate the solution seven out of ten.

Many teams use Jenkins here. Some may use it on the cloud, and others may use it on-premises. I'm using the latest version of the solution. I'd rate the solution nine out of ten. The reason we love it is the huge amount of connectors that Jenkins has. It has seamless connectivity with literally every product from Octopus, and you can integrate everything into your pipeline seamlessly. That was the reason we switched to Jenkins.

I give the solution eight out of ten. The solution has several advantages over its competition because it doesn't require a license, is easy to integrate, and there are a lot of free resources and information available online. I recommend the solution and suggest to anyone thinking about using it to first familiarize yourself with the plugins and know what it is you want to get out of the product before installing it. There are over 2000 people in our organization and over 80 percent of our project use this solution. The solution has readily available documentation and support that can be found online.

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.

I would recommend Jenkins to potential users. You can use Jenkins with other products and make anything you like. On a scale from one to ten, I would give Jenkins a ten.

I rate this solution a seven out of ten. My advice is to go for the proof of concept. Go with the open source and follow this solution because it works. If you get a paid version, you'll have a trial version for some days. If it suits your requirements, then you can purchase it. Otherwise, if you purchase it and it does not meet your needs, then it's a waste of money. See how you can model the integrations, the automation, and the frameworks and then go further into the interface solution. The solution is good but it can be improved by including automated mobile reporting integrations.

My advice to others is they should use Jenkins in the cloud. If they try to access the solution outside of the cloud environment, you need to configure whitelists and other configurations and keep an eye on them. I rate Jenkins a seven out of ten.

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.

I would rate Jenkins eight out of ten.

I rate this product a four out of ten. I would advise people using this product for the first time to review the provided documentation and watch some YouTube videos on the setup process while trying to understand the platform itself. The documentation is essential as it allows for a better explanation of some features and YouTube assists with troubleshooting. The product is affordable, but the user interface needs to be improved.

I rate Jenkins a seven out of ten.

I would recommend Jenkins to anyone thinking of implementing it into their organization. Overall, I would rate Jenkins a nine out of 10.

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.

I would recommend this solution to others. I rate Jenkins an eight out of ten.

The time has come for companies to move to containers. I believe that Kubernetes services are based on the customer's needs in a secure manner. People will go with AWS or GCP. I would rate Jenkins an eight on a scale of one to ten.

The solution can be on-premises or in the cloud. I'd recommend the solution to others. I'd rate it ten out of ten.

I recommend Jenkins to others. I rate Jenkins a nine out of ten.

I rate Jenkins eight out of 10. It's a scalable, open-source tool with multiple plugins. It's easy to use and set up. I don't rate it 10 because there is room for improvement in terms of the cloud and related capabilities. If somebody wants to use Jenkins, they need to first consider the scope. What is the scope, and what tech are you using? Jenkins is easy to set up, and we can integrate it with multiple technologies, whether a .NET application or anything else. We can deploy the code and can run with that.

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.

Jenkins is stable, user-friendly, and helps with continuous integration. As of today, I can't see any tool that's better than Jenkins. If you have very few APIs which can be deployed manually, I wouldn't recommend Jenkins. However, I would recommend it for those with multiple APIs and many clients, who are doing code changes on a daily basis. I would give Jenkins a rating of seven out of ten.

As people are using it, they should come to the community and provide their input so that the community can grow better. I would rate it an eight out of ten.

For the development environment, we are using the on-premise infrastructure. For some customers we are also using on-premise; for other customers, we are using the cloud. We have branches in Egypt and branches in Dubai that are using Jenkins for the whole automation process and we're really enjoying using it. I would recommend the solution to others. I'd give it a rating of seven out of ten.

I'd rate Jenkins about six out of 10 because it doesn't have much out-of-the-box integration. Everything needs to be done manually. On the other hand, it's free, so that makes up for the shortcomings. It depends on an organization's needs and budget requirements because it's not something I pay for. I would recommend it for certain use cases. It depends upon the project. For example, Jenkins might be suitable for a client who doesn't use a cloud provider to deploy their CI/CD pipelines, and they're deploying on their on-prem system. Also, if they're in their POC phase and are unsure how much budget will be allocated to the project, I definitely recommend Jenkins to be their first-go solution for a CI/CD pipeline.

My advice to others is to explore Jenkins well and it is integrated with the scripting site. Teams should explore the scripting part of the Jenkins because everybody's nowadays is writing pipeline as a code for automating their operations. They should try to utilize the new feature provided to them, such as pipeline as a code. It does not matter what solution they are using, such as Microsoft Azure DevOps or Amazon AWS DevOps, Jenkins will integrate with other solutions. They should try and use Jenkins even if they're using some other tool. I rate Jenkins an eight out of ten.

I would rate Jenkins between seven and eight because I'm not that much of a GUI user, so I can use it. And if I have my configurations in place, I don't have to go inside and look at the UI again. It's a good solution for us.

I would rate this solution as eight out of ten.

It's important to know your requirements before implementing Jenkins. It's a good tool for integration and automation in an organization. I rate the solution eight out of 10.

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

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.

Jenkins is a great solution if you're looking at automation because it reduces manual work and improves performance. If you deploy it on cloud, then performance is improved further. It's worth reducing dependency by targeting a one-build solution for Jenkins. I rate the solution eight out of 10.

I would recommend this solution to others. I rate Jenkins a nine out of ten.

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.

I would recommend this solution. I would rate Jenkins a seven out of ten.

When selecting a solution I would advise checking their budget, the volume size they are performing, and what full-stack they are performing on. Based on this information, they can better determine what solution is best for them. If they have a low budget this solution would be great for them. I rate Jenkins an eight out of ten.

I would recommend this solution, but it depends on the project. It has a lot of support, and it's been in the market for a long time. Many big organizations also use it. On a scale from one to ten, I would give Jenkins a nine.

For a person who wants to get started with Jenkins, I would advise initially deploying Docker with Jenkins. You can also create a shared library in Jenkins. You should have some basic knowledge of the Groovy script. I would rate Jenkins an eight out of ten.

I would rate Jenkins 9 out of 10.

I would recommend this solution. It is good for small companies but not for big companies. It has a good interface and was easy to customize. We were also using another plug-in to enhance the user interface. I would rate Jenkins a seven out of ten.

We recommend having the proper infrastructure, and to ensure the maintenance of the server is performed.