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.

In Kubernetes, we use node-based architecture with nodes and pods and follow practices like RBAC and rollback. Multiple pods can run concurrently. We benefit from Kubernetes' ability to autoscale pods and use horizontal pod autoscalers to adjust the number of pods based on metrics like CPU or memory usage, ensuring efficient resource allocation and stability under load.

We sometimes face challenges during version upgrades, such as failures when migrating Kubernetes versions. 

Additionally, changes made by AWS services, like those in CodeBuild, require investigation to assess impacts on our applications, which can lead to challenges.

I've been using Kubernetes for the last three years. Additionally, we received an email from AWS mentioning changes starting on January 30th.

We do robust testing before deploying to production, undergoing multiple phases like testing, staging, and acceptance, to ensure stability. We rarely encounter production bugs, focusing on enhancements and UI changes instead.

Kubernetes provides scalability by using horizontal pod autoscalers that adjust the number of pods based on CPU or memory usage. The load balancing service distributes traffic across multiple pods, ensuring scalability and availability without straining any single pod.

I rate Kubernetes eight out of ten. 

I would recommend it to others as it is widely used.

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.

Jenkins can sometimes run slow, especially when restarting after a plugin installation or when returning from a pipeline view to the dashboard. This slow performance is a challenge I have observed.

I have been working with Jenkins for a year since I began my career.

I find Jenkins to be very stable. I have not encountered any significant stability issues.

I have not faced any scalability issues with Jenkins. Any problems we encountered were due to instance limitations, not Jenkins itself.

I have not used Jenkins support as I am a junior developer and usually rely on my mentors, seniors, or friends for help. I also search the internet and YouTube for solutions when needed.

Positive

Setting up Jenkins was straightforward for me. I open it in an EC2 instance and then install Java and Jenkins. It's easy to maintain, and the maintenance process is simple but requires regular updates to the pipeline.

I have limited experience with GitHub Actions, using it for certain projects as a convenience because we already use GitHub for source control.

I recommend Jenkins, especially for beginners starting with DevOps pipelines. It is easy to get started with and understand. Learning about Jenkins' advanced features, such as dealing with folders and build pipelines, is important before diving into projects. 

I rate Jenkins a nine out of ten due to its ease of use and features.

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.

The major drawback with Jenkins is the lack of support. If any issues arise, we need to fix them on our own, either by upgrading, going with a new version of Jenkins, or rolling back to the previous version. 

Unlike my previous company where we used Azure DevOps, where issues could be logged directly to Microsoft for a fix, this kind of support is not available for Jenkins.

I have been using Jenkins for almost one and a half years since moving from my previous company.

Jenkins is a stable product. From a rating standpoint, I would give it around seven to eight out of ten.

In terms of scalability, we have to rely on in-house efforts and online resources since Jenkins is open-source and doesn't offer built-in support. I would rate scalability around seven out of ten.

Support for Jenkins is not available as it is an open-source product. We need to rely on our own resources or external information sources like Google.

Neutral

In my previous company, we used Azure DevOps primarily since it was a Microsoft partner company.

We took support from a different vendor to write a script using Ansible, which helps us deploy Jenkins using new versions and all that.

Jenkins is used in many companies to save money, especially within R&D divisions, by avoiding the expenses of proprietary tools.

Jenkins can be compared with Azure DevOps and CircleCI, but Azure DevOps comes with comprehensive project management and ticketing, unlike Jenkins.

I would rate Jenkins between seven and eight out of ten. It is a good product for those who choose it based on their research; however, it lacks support for troubleshooting issues.

I can install Jenkins for integration from multiple developers and automate application delivery, staging, and production environments.

Jenkins is very useful. I can install Jenkins for integration from multiple developers and automate application delivery, staging, and production environments. It's very easy.

I do not have any notes for improvement.

The scalability of Jenkins is good.

I never have had to contact their support team for any reason.

I also considered using CodeDeploy or Jenkins.

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

We used Jenkins for integration purposes, primarily for integrating with version control systems like Git and build tools such as Maven. Later, there were plans to use it in Docker deployment for Docker containers. 

I configured environments for non-production, production, and development in the pipeline. 

I also used Jenkins for a Bluegreen deployment strategy, quality assurance with SonarQube, and artifact storage in JFrog Artifactory.

In our previous company, Jenkins was used for complete automation of build and deployment in a project. From part of automation and customization, I was involved in the project.

The most valuable feature of Jenkins is the plugins available. You name any tool, and there is a plugin available for it in Jenkins. 

Also, the ability to customize these plugins is valuable. Its user-friendliness stands out, especially in its user interface which allows easy installation and configuration.

Jenkins could improve in areas related to Kubernetes and Docker container integration, like machine allocation of nodes and Marshaling integration improvements. Making these aspects more robust would be beneficial.

I have been using Jenkins for around five years now.

Jenkins is stable. Any tool can have latency of a few seconds, but I would rate Jenkins four and a half out of five for its stability.

Jenkins is not as scalable compared to container solutions like Docker or Kubernetes. While it can be configured at the server end, the other solutions offer more robust automation and scalability.

My team handles technical support for Jenkins when necessary. However, since I moved into AI and machine learning projects, I haven't been closely involved with technical support issues.

Positive

The initial setup of Jenkins is very straightforward and not difficult.

By installing Jenkins in a master-slave environment, there is significant cost saving, making it a cost-effective tool compared to other CI tools.

I do not have extensive knowledge on the pricing or licensing aspect as I used Jenkins for free at the local machine level. However, it is generally regarded as cost-effective.

I would rate it a nine out of ten.

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 find Jenkins beneficial for its plugin downloads and ease of integrating all the tools available in the market. It's a powerful tool for CI/CD.

Creating a new SonarQube project requires a separate job, and we've encountered some integration issues with Docker and the need for better vulnerability checks.

I have recent experience with Jenkins from about six months ago.

We have faced downtime due to issues with the node setup and agent management, which are handled by our platform team.

We find Jenkins to be scalable since our setup includes different servers, allowing it to handle multiple jobs and applications.

If there is a problem with pipeline failures, we debug the logs and provide resolutions. We also track the code with the developers to try and resolve any issues.

Positive

I switched from Jenkins to Tekton due to specific project demands and client requirements. I'm currently working with Tekton on my current project.

The initial setup was easy. We used Amazon EC2 to host Jenkins, which made it simpler to deploy.

We have a platform team for Jenkins, who manage the nodes, agents, and merge nodes.

I recommend incorporating Jenkins into projects to make deployment easier and because of its easy integration with other tools.

I'd rate the solution nine out of ten.

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.

Jenkins is particularly valuable since it saves time by automating manual tasks. It also securely stores secret information, supports a wide range of integration plugins, maintains deployment history, and allows seamless user onboarding with LDAP connectivity. Additionally, the setup is straightforward.

There are some issues with Jenkins, especially with the SIP job. When you run the SIP job, it triggers child jobs in a sequence, yet often fails post-completion. These issues are open in Jenkins, and while there are fixes and it remains usable, improvements are needed in this area.

I have around eight years of experience working with Jenkins.

I would rate Jenkins' stability as seven out of ten. The software is quite reliable, but there is room for improvement.

Jenkins is scalable; you can add multiple worker nodes to manage load effectively. I would rate its scalability as eight out of ten.

For Jenkins, being an open source solution, there is no official technical support available. You can raise issues in GitHub, however, it's primarily supported by an open-source community.

Neutral

Before Jenkins, we used shared groups to deploy, which was mostly a manual operation involving automated scripts. Jenkins replaced this by automating processes, which enhanced efficiency.

The initial setup of Jenkins is fairly easy, especially for someone with my background. It's a straightforward process.

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.

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.

Jenkins is very customizable. You can specify exactly what you want, including permissions and controls. It is an excellent tool for managing CI/CD and GitOps.

Adding support for OIDC and internal user databases simultaneously would improve Jenkins. Currently, you can choose only one method of authentication, which is limiting, especially since we have our own SSO server.

I've used the solution since the beginning of this year.

We had issues with stability, like connectivity problems between Jenkins master and worker nodes, depending on the infrastructure. Additionally, it often requires frequent updates, which can be inconvenience.

Jenkins is quite scalable, especially if hosting on Kubernetes. However, it requires setup, including adding necessary plugins and dealing with Docker in Docker configurations. With Jenkins, scalability is good, but you need to handle it yourself.

To set up Jenkins, you need experience with Groovy and an understanding of how Jenkins works, including pipelines and stages. Almost everything is declarative, requiring some learning and time investment.

Jenkins is open source and free to use. You simply download it, install it on your server, and it manages your pipelines.

Although we use Jenkins, I would recommend considering cloud-based CI/CD tools like CircleCI for an easier setup. However, CircleCI also has challenges.

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.

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.

Integrating Jenkins with other tools or solutions has presented some challenges. For instance, when attempting to integrate Jenkins with Kubernetes, I encountered numerous errors, which took several days to resolve. In Jenkins, adding a feature typically involves incorporating the repository feature separately. Jenkins lacks built-in Git repository functionality, necessitating an external Git repository to store Jenkins manifests.

In contrast, GitLab offers an integrated Git repository and pipeline runner, streamlining the process. One improvement for Jenkins could be integrating a Git server, simplifying the management of CI/CD pipelines. Currently, with Jenkins, modifying pipeline manifests requires navigating to a separate Git repository. In GitLab, however, manifest changes can be made directly within the repository.

I have been working with the product for two to three years. 

I've experienced some performance issues with Jenkins. It's using a PostgreSQL server to store its data, and currently, we're facing slow loading times for the tool pages. This slowness is due to many teams currently using it, which strains the database and slows performance. Unfortunately, we haven't been able to resolve this issue despite working on it for a year. As a result, loading the pages can take up to 15 seconds.

Scalability is dependent on the database. The solution uses PostgreSQL as the default option, although other options are available. However, in our case, PostgreSQL's performance is currently quite low, which affects scalability. My company has 300-400 users. In our company, Jenkins is more widely used than Tekton. Approximately 70 percent of our organization's members utilize Jenkins, while the remaining 30 percent use Tekton.

If I compare Jenkins with Tekton, Jenkins has a more mature dashboard, which allows for control over pipelines. Additionally, Jenkins offers numerous plugins that facilitate integration with other tools. For instance, integrating your pipeline with an email server is straightforward with the appropriate plugin, making integration much easier than with Tekton.

The initial setup process isn't straightforward. While installing the Jenkins server is easy, adding agents for it can be complex. Setting up the Jenkins server is quick, often done through a Docker image. However, adding new agents, essential for tasks like building CI/CD pipelines, is not as simple. In my experience, it took considerable time to add agents, whether they were Kubernetes agents or agents on Linux machines, to the Jenkins server.

When I first installed and used the tool, it took me around three days to set up a production-ready Jenkins server. It was my first time using it. However, compared to other tools like Tekton, which took me only about half a day to install and set up for using pipeline and CI/CD workflows.

The tool's maintenance costs are low because you can upgrade the Jenkins server and agents without incurring additional costs. It's not dependent on the underlying system, which keeps operational costs down. I believe Tekton's cost of operations is lower.

Compared with Tekton, Jenkins can help save costs and improve efficiency in our project. It supports a library feature, allowing us to reuse code and avoid repetitive tasks, ultimately reducing operational expenses.

The tool is open-source. 

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. 

Jenkins is a tool for continuous integration and continuous deployment. It is open-source automation software that aids in deploying software, executing tasks, and creating pipelines. Jenkins is widely used to automate the building, testing, and deployment of applications through pipelines designed to streamline the development process.

It offers continuous deployment and continuous testing. It enables us to figure out anything.

The user interface could be improved, and its reporting capabilities need enhancement. The plugins could be more effective. Additionally, monitoring Jenkins can be somewhat challenging.

I have been using Jenkins for three to four years.

The product is stable.

The solution is scalable, but integrating it with other servers is a bit complicated. Seven people are using it.

The initial setup is challenging. It is deployed within the target environment and acts as middleware.

If we want to automate the IPP, the best approach is to start with Jenkins because it provides a solid foundation as an open-source automation tool. Once we have established our basic automation with Jenkins, we can consider migrating to cloud environments such as Azure or other cloud platforms for scalability and additional features.

If there are constraints, especially when starting with basic needs, Jenkins is the best open-source tool because it is free and works like other tools. However, with the rise of cloud technologies and powerful solutions, Jenkins remains a strong choice if our system is on-premises.

Overall, I rate the solution a six out of ten.