Jenkins Reviews

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.

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

There are many use cases for Jenkins. We have an AWS infrastructure in which we have created templates for the provisioning of the infrastructure, and for the infrastructure network appliance, we use Jenkins.

For the builds, we use Docker images, Maven, Gradle, and other builds. We send all the build environments to the Artifactory Servers running Jenkins. 

For any deployments to the systems, such as any standalone machines, Kubernetes cluster, or Auto Scaling groups, we use the Jenkins. 

If a Kubernetes cluster is ready and you want to have other external configurations we use Jenkins for all of the configuration setups.

Jenkins can be used to check vulnerabilities of any system or Docker images.

The most valuable features I have found are it can integrate other services as a plugin. For example, if you want to integrate GitHub, or third-party tools, such as Prisma scan, you can have them as plugins and you start using them. 

Jenkins can be used for elastic management, if you have any sensitive data or credentials you can use them across the environment. Additionally, the solution is easy to use and can be used across multiple use cases.

The solution could improve by having more advanced integrations.

I have been using Jenkins for approximately four years.

The solution is stable. However, if you have any network interruption or any server failure it will not be stable.

I have used the stand-alone Jenkins systems and I have other slaves configured with different systems or Docker containers and it has been operating well.

The scalable depends on the environment, if you want to have scalability it is possible. However, if there was a specific option to scale Jenkins systems it would be great.

We have approximately 250 users using this solution.

I have not used the technical support from Jenkins but I have used the online forums which have been helpful in answering questions.

I have previously used GitLab and Azure DevOps tools. I have found them both to be more complicated than Jenkins and this is why I switched. I am more familiar with Jenkins and this is another factor of why I use it.

The installation is straightforward. All you have to do is update your repository and then install it. There are certain configurations needed after the installation, such as providing the secret key, accessing the server, managing the user access for separate groups, for example, development, performance, and QA groups all need different access levels assigned. It does not take more than 10 minutes.

We did the implementation ourselves. Additionally, we can create scripts to do the configurations, this reduces the time needed for us to do them individually.

I am a DevOps engineer and we configure or automate deployments, schedule deployments, and then giving access to certain teams, such as the QA teams. They login in the morning and then if they want any new deployments, they can get it done. 

There is a development team to a certain environment, such as test environments, where they can test their code. They have a particular job and can do the deployments by themselves.

Jenkins is a free open-source server.

I would recommend this solution to others.

I rate Jenkins a 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.

This solution is open source and we use it for the entire bill pipeline - for building different languages, for running reports on code coverage, running our QA tests, automated tests, and for deployment. We are customers of Jenkins and I'm head of infrastructure. 

The advantage of this product is that it brought automation to the company. Instead of manually billing, manually trying to run tests, it now happens automatically. 

The best thing about Jenkins is that it's such an open community, and it has a bazillion plugins which is a neat feature. Anything you want to do, someone else has probably already done it.

Despite there being a whole lot of community input on the solution, nobody is providing professional services around it. Jenkins itself is a very small company but it would be great if they could host and offer some kind of SaaS product which would provide an organizational structure of some sort.

I've been using this solution for 13 years. 

Stability is not top notch but it's pretty good. 

The solution is very scalable, I probably have around 60 people using it, mainly developers checking whether there are any errors. We have around 10, 15 QA people, power users, and  another 40, 45 developers looking at it. The solution is being extensively used but we only need one person to deal with maintenance. 

The initial setup was straightforward and didn't take too long, maybe a few days. Implementation was carried out in-house.

It's important to take the time to research the solution and find what's right for you. Since it's so customizable, there's a million ways to do things and since there's no professional services that says this is the right way, you have to figure it out on your own. Take that time, do the research, try things out. Make sure it works before you go ahead and put it into your whole organization. This solution touches the bases of everything we need to do. Professional services aren't there, but that's the only downside. Other than that, we're very happy with the product. 

I rate this solution a nine out of 10. 

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.