Jenkins Reviews

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.

As a Software Engineer, I deploy critical application code using the critical infrastructure consisiting of Jenkins and Terraform. I also manage AWS services like EC2, RDS, and ELB. I am responsible for handling on-call issues, deploying data bundles to various environments, and I operate on a weekly or bi-weekly deployment schedule based on requirements. We follow the Agile methodology and tracking work with tools like Jira.

We avoid application downtime by using Kubernetes' scaling features, such as horizontal pod autoscalers and load balancing services. This ensures our application handles increased requests efficiently and remains robust and scalable.

I use Jenkins as a CI/CD tool. We create pipelines using Jenkins, with stages for Maven builds, Docker image builds, SonarQube integration, and deploying the image to a Kubernetes cluster, AWS EKS.

Jenkins has made the developers' work very easy. They commit to the remote repository, and everything happens automatically, which simplifies our automation and continuous integration.

I'm using Jenkins for CI/CD pipelines. We have around 400 dashboards and BI applications that need to be deployed when we make changes and push it all out on GitHub. 

I create webhooks from GitHub to trigger the Jenkins pipeline, which runs a script that I'm writing in Python. This deploys the applications to their respective application servers.

Jenkins allows us to automate deployment, so I no longer have to do it manually. That's the primary use case. The other advantage of Jenkins is that it's open source. It was free for me to download and install. It's a product that's been in use for many years, so I can find a lot of support online for any issues that I may encounter while configuring anything for a given use case.

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.

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.

Mostly, the company is a product-based company, primarily in the hard disk and flash business. A majority of the work involves firmware development. We are using Jenkins for the build process like CI pipeline. We are not using the CD pipeline in this case, only for building the artifacts.

Jenkins is a CI/CD tool and is the most robust tool. Although it comes from the open-source family, most companies use it just for cost-saving purposes. We are using it for the company's own infrastructure, not to serve a client. The company is into R&D stuff over here in India. In R&D possibly, it could be a reason they did not want to invest much by buying the product from different vendors other than going for open source.

We use Jenkins for CI/CD and infrastructure automation. It is primarily used for application deployment, and we deploy Docker containers to our Kubernetes cluster.

For CI/CD and automation, it is more application deployment, and we use it to deploy Docker containers to our Kubernetes cluster.