Jenkins Reviews

My main use case for Jenkins is to automate deployments of my application and my serverless functions. I am using Jenkins for three scenarios: first, to deploy serverless applications, second, to deploy my applications, and third to deploy Terraform resources. I have multiple pipelines that pull from the repo where my application is hosted on GitLab. It is connected to GitLab, and as soon as I push my code, Jenkins sees the code changes and deploys it to the environment, whether it's serverless function code, application code, or Terraform deployment.

I have covered my main workflows regarding Jenkins.

Through Jenkins, we have fastened our deployments, enriched our integratability options, and added numerous features, which have reduced our deployment time by 50 to 60%. We no longer have to manually deploy applications; we just trigger the pipeline and Jenkins handles the rest.

By reducing deployment time by 50 to 60%, we are able to ship code to production more quickly—previously it took six to seven hours, and now it takes only about one hour to deploy an application. This efficiency allows developers to focus solely on their code without having to manage the DevOps side of applications. Jenkins enables them to just write code, push it to the repo, and then Jenkins takes care of everything. This focus on coding instead of CI/CD tasks has greatly increased productivity, especially because we are utilizing cloud-managed plugins that allow us to build pipelines in containers and dispose of them right after execution, saving costs.

The best features that Jenkins offers me are high customizability along with the support of Groovy language, which allows me to write my own functions and logic to deploy applications and configure the pipeline according to my use case. Its high integration capability with many plugins is also a significant advantage.

For example, we have certain cloud functions running on Google Cloud Run, and we deploy those in the form of containers. Jenkins is highly integratable with Docker through plugins, so we installed those plugins in Jenkins and provided the credentials and logic for execution. Additionally, we have a Bitbucket environment and AWS deployments where we also use Jenkins' strong AWS plugins to deploy resources effectively. Thanks to these plugins, it's easy to deploy rather than creating custom logic.

I have covered pretty much everything about the features of Jenkins.

Jenkins has many outdated plugins, and several are paid, which can be unnecessary. Better plugin maintainability is needed, and given the AI advancements today, AI support in Jenkins would be beneficial. Additionally, some error messages from Jenkins can be misleading, and the UI seems outdated, so there are areas for improvement.

The documentation for Jenkins sometimes lacks examples for implementing certain functions, so it could be reviewed and improved.

I have been using Jenkins for the past three to four years.

Jenkins is highly stable and widely maintained.

Jenkins is scalable, but not as greatly scalable as other market solutions; it does not operate on a master-slave architecture that allows for automatic failover. While deploying agents can utilize a master-slave structure, Jenkins itself requires manual intervention for the master.

Jenkins is a community-managed tool, so there is no native support. However, there is a helpful GitHub issues section where we can discuss problems with other users.

We were using native solutions such as GitHub Actions and manual scripts to handle deployments before switching to Jenkins. The downside of those solutions was that while GitHub Actions offers high integration, it does not allow for private setup; everything runs in the GitHub cloud. We needed to run Jenkins in our environment, keeping data secure and unshared, allowing us to operate independently.

We have seen a return on investment since implementing Jenkins. Before its introduction, developers had to manage both CI/CD and coding, which hampered productivity and prolonged the time taken to ship code. Now, with Jenkins, they can focus on coding, push code, and Jenkins automatically manages the process, ensuring security and efficiency, thus improving productivity and decreasing shipping time. We also enjoyed greater customer satisfaction and saved money in the process.

We are using a community version of Jenkins and did not purchase it through the AWS Marketplace.

The main cost for using Jenkins is related to the server it is hosted on and the allocated capacity. While Jenkins is stable and can run on minimal resources, larger environments might incur higher costs due to the need for high-end VMs to run build agents.

We evaluated managed and cloud solutions such as AWS Pipeline, GCP Cloud Run, Cloud Deployment, and Cloud Build before deciding on Jenkins.

Jenkins is widely used, rich in features, and helps to significantly reduce manual efforts. Its capability for writing functions is outstanding, making it a valuable tool. Currently, Jenkins does not have AI capabilities, although the tool is being evaluated for potential AI integration, and it is highly secure as we deploy it in our own environment without external exposure.

Jenkins is highly accurate and reliable; however, sometimes outputs can be misleading due to outdated plugins.

Jenkins is deployed in our organization on a public cloud, specifically in a private VM. We use both AWS and GCP as our cloud providers for Jenkins deployment.

I would advise others considering Jenkins to use it due to its rich feature set, private hosting capability, and high integrability. It serves as a solid alternative solution. I would rate Jenkins a 10.

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.

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

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.

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. 

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.

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.