Jenkins Reviews

I use Jenkins for CI/CD pipelines. 

Jenkins's automation and orchestration features have significantly improved workflows by automating various processes. Initially, it did not support YAML manifesting or GitOps, but recent versions have introduced these capabilities. Now, the tool supports importing manifest files from Git repositories, enabling the implementation of GitOps pipelines. Compared to other tools like GitLab, it has become a mature tool for running CI/CD pipelines.

While some integrations were difficult and time-consuming, others were more straightforward, requiring only a few clicks. The tool benefits from a community of plugin providers that offer various plugins for various functionalities.

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.

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.

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.

I primarily use Jenkins for creating a pipeline for all applications, from checking out from GitHub to deploying the app. It involves updating the code in GitHub and using GitHub's Argo CD action for deployment. 

In our DevOps operations, we utilize Jenkins for automation to check out code from GitHub, scan vulnerabilities, check dependencies, and create Docker images.

Jenkins is free and open source, which is beneficial for any company. The ability to use parameters and the option to categorize pipelines as folders or views is useful. 

Additionally, its building and configuring capabilities are similar to other tools. I find Jenkins stable and have not faced scalability issues, only encountering problems with instance limitations, not Jenkins itself.

I primarily handle Jenkins in my organization for tasks such as enabling CI/CD and infrastructure deployment. We deploy applications and automate processes using the open-source Jenkins solution rather than CloudBees.

Jenkins has been a good fit for our processes. We have biweekly sprints with continuous integration and delivery, enabling us to automate many tasks. This improves efficiency and fits well into our requirements.