In our CI/CD pipeline, we rely on Jenkins to trigger various tasks related to the Telco Cloud infrastructure. It's an essential tool for managing our infrastructure tasks efficiently.

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.

Support should be provided at no cost, as there is no free support available for any of the free versions.

I would rate its stability capabilities eight out of ten.

It provides solid scalability.

The initial setup is fairly straightforward. I would rate it eight out of ten.

Deployment is straightforward for us because Jenkins is open-source. We simply install it on one of our virtual machines, and it works seamlessly.

It is an open source.

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 used for continuous automation of the various stages of the software development life cycle, such as building, testing, and deploying code chains. Jenkins supports continuous integration, allowing developers to integrate their code chain into a shared repository multiple times in a day.

Jenkins has a large number of plug-ins available for source code management, build tools, and testing. Jenkins integrates with various version control systems like Git and Bitbucket. Since it has a pipeline, Jenkins supports the creation of complex builds and deployment for a flow using the pipeline plugins.

Jenkins provides security features such as user authentication, authorization, and role-based access control. The solution integrates with external identity providers for authorization.

Jenkins optimizes the CI/CD process, enhances automation, and ensures efficiency and management of our build and deployment pipeline. It is easy for somebody to learn to use Jenkins.

Jenkins should adopt the Pipeline as Code approach by building a deployment pipeline using the Jenkins file. The solution should also include parallel build, artifact management, and automated matter testing.

I have been using Jenkins for one year.

Jenkins is a stable solution.

More than five people are using the solution in our organization.

The solution’s initial setup is easy.

Jenkins is an open-source platform.

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.

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.

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

I have been working with the product for eight years. 

I rate Jenkins' stability a six out of ten. 

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

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

We use the tool's free version. 

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

We mainly use Jenkins as a CI/CD setup for our development, as a build tool to build, test, and deploy.

There is room for improvement in the setup. The setup could become easier.

Another area of improvement is the user interface. Jenkins could simplify the user interface a little bit because it sometimes creates too many features cramped in the UI. So we would like to have a bit of a streamlined user interface.

I have been using Jenkins for a couple of years. 

It is a stable solution.

We had some issues with scalability. Our organization has around 5,000 end users because Jenkins is our primary CI\CD tool. 

The initial setup is not that complicated, but also it's not very simple. You need to educate yourself a little bit.

It is a cheap solution. 

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.

We use Jenkins in CI/CD pipelines. 

Jenkins integrates with multiple tools like Bitbucket and makes life easier. We don't have to write a lot of code since a lot of libraries are available. 

The product should provide more visualization as to how many pipelines are performing and how many builds are happening. It should also integrate with Kubernetes and OpenShift. 

I have been working with the solution for one and a half years. 

I would rate the product a nine out of ten. 

Jenkins is pretty scalable and I would rate it an eight out of ten. My company has more than 100 users for it. We use the tool every day. 

We report to our infrastructure team about the plugin issues. 

We wrote our own custom scripts before Jenkins. 

The tool requires maintenance whenever upgrades are available. 

We use the tool's open-source version which is free. There is an enterprise version which is expensive but comes with better support. 

I would rate Jenkins a nine out of ten. 

We use the solution for continuous integration and deployment.

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.

The most valuable feature of the solution is its integration between different tools.

The dashboard needs to be improved. Though the access management and authentication functionalities are present, the dashboard and UI could be more user-friendly. The product has many plug-ins. Users have to go through the documentation to be able to use the product.

The UI must be more user-friendly. The information should be available in the dashboard itself. The users shouldn’t have to refer to the documentation. When a user hovers over the elements on the dashboard, it should reveal information about them.

I have been using the solution for the past three years.

The tool is very stable. I rate the stability an eight out of ten.

The tool is highly scalable. I rate the scalability an eight out of ten. We have around 600 to 700 users in the organization. We are using the tool 24/7.

CloudBees provides us with support for the product. It takes time to get a response from the support team. The response time for support must be reduced.

Neutral

The initial setup of the solution was complicated. I rate the ease of setup a six out of ten. We had to refer to additional materials to understand how to incorporate and integrate plug-ins with different software and endpoints. The setup and planning process took around one to two days.

To deploy the solution, we need a Kubernetes cluster. We implemented the solution in-house. We need one or two DevOps administrators to deploy the solution. Depending on the workload, we need five to six people to maintain the product.

We have saved time on deployment. Once the developers add new features to the application, the deployment process takes only a few minutes. We have received an ROI of almost 80% to 90%.

The product is expensive. The open-source version is free, but small companies would not be able to afford the cloud-based version. I rate the pricing an eight out of ten. Additionally, we have to pay for the product’s support.

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.