Jenkins Reviews

We have multiple job templates available. You just need to find the best template for your needs. If you just want to do a Maven build, there will be a more suitable template there. For something else, if you just have one rebuild and you want to deploy it from the server, there will be some other job template available. We have multiple job templates, so we need to configure according to that template and then it's okay.

The solution is deployed on-premises. About 15% of my organization is using this solution. It's basically used by the DevOps engineers. Not all the developers use it.

With Jenkins, the pipeline will take your code from any versioning system like GitHub or Bitbucket. All the security scans can happen in one go and then all the tests also get run. You can just build one container in it and deploy it.

For this solution to be a 10, it has to be a lot more stable. Maybe the public version of Jenkins is stable, but in our case it's not stable. There is a knowledge record, but you still need to figure out the way to configure it initially. It has to be easier. There should be some indication that an error is not caused by Jenkins.

I have been using this solution for a year and a half.

Because we are using in-house tools, it's a little bit unstable.

It's very scalable.

We haven't needed to call support. If we have any issues, we contact HSBC's support team or the one who created the template.

Initial setup is difficult. From start to finish, deployment takes an hour and a half.

We are using in-house tools.

Jenkins is open-source.

I would rate this solution 6 out of 10. 

I have less knowledge of the raw Jenkins, but Jenkins is doing almost all the stuff that I want it to do, but it's not a 10 because of the difficulties to configure it, to make it work, to do end-to-end, and then the stability.

You should first find out all the requirements that Jenkins is doing. You need to find out if you have any coding issue or if Jenkins has any issue. Now I train people to use it, and normally these are the issues that I find. There are many occasions where there is an issue with code but it's not always that Jenkins is wrong; sometimes it's the code that is breaking.

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.

We use this product as an open-source CI/CD. It allows integration, building pipelines, and even linking them to Azure or AWS platforms. It is an open-source tool. However, I wouldn't call it a public cloud. I would refer to it as an open-source tool for continuous integration and deployment. It can be integrated across every platform.

Our primary use case for this solution is creating pipelines for some projects we work on. Additionally, we use it to build pipelines and provide them with commands. For example, if we want to make a Docker image or send the deployments to Azure then we can integrate them into the Jenkins app service instead of Azure DevOps.

The user interface could definitely be improved, and I rate it close to zero. It isn't very good, and I am sure why it has not been worked on. The user interface could definitely be improved.

We have been using this solution for approximately a year and a half and are currently using the latest version.

The solution is stable but it is slow. It is a free service so I can't complain about the time it takes.

The solution is scalable and concurrent users have access to the platform. Currently, only a few people in our company are using this product.

I have not contacted customer service and  support.

The initial setup was difficult. It is not easy to comprehend, and I recommend having a hands-on tutor or experience for you to be able to use it effectively. Additionally, the documentation is not helpful, as it is not user-friendly. I am unsure if this is because it is an open-source product, but it can definitely be improved.

It took approximately two hours to set up from scratch. In order to create the Docker image dependencies that need to be integrated need to be checked. The required keys also need to be identified because some SSH keys might be needed.

We chose this solution because it is in line with the budget and customer preferences. 

I rate this product a four out of ten. I would advise people using this product for the first time to review the provided documentation and watch some YouTube videos on the setup process while trying to understand the platform itself. The documentation is essential as it allows for a better explanation of some features and YouTube assists with troubleshooting. The product is affordable, but the user interface needs to be improved.

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.

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.

As an administrator, I manage Jenkins. The development team uses it more frequently for automation and CI/CD.

Jenkins is a very good automation tool for building and deploying CI/CD. It is a good building tool and is the most popular tool for Java and microservices projects. Jenkins has a lot of built-in packages and tools.

The support for the latest Java Runtime Environment should be improved. We usually need support with Java Runtime Environment during the installation and administration of Jenkins.

Jenkins should add support for Java Runtime Environment.

We have been using Jenkins in our organization for the past five years.

Jenkins is a stable product.

The on-premise solution is used by seven people in our organization, including five people from the development team and two from infrastructure administration. So around seven people use Jenkins on-premise.

So far, I have never raised any support requests for Jenkins. I go through the Google online forum to solve the issues I usually face because it is an open-source deployment tool. However, I can rate it a six or seven out of ten.

Neutral

The setup is not that hard. If you are familiar with the Linux system and the Java Console, it is very easy to set up. It is easy to install and deploy.

Jenkins is an open-source tool.

Jenkins is Java-based. Our organization recently upgraded to Jenkins 2.390. We deploy Jenkins into VMware vCenter machines.

We use Amazon Web Services for pipeline automation on the cloud. I would recommend Jenkins to others. Jenkins is a popular CI/CD tool commonly used by DevOps teams. I rate Jenkins an eight out of ten.

The solution is a continuous integration tool.

The most valuable features of the solution are the vast number of resources available online to all users and that it is open source.

The solution can be improved by introducing a handbook describing the variety of plugins that are available and what each one is used for. There are so many plugins if you don't have experience with them you can't create a properly working CI pipeline. The addition of automated plugins can improve the solution.

The solution's UI can use a facelift and the logs can use more detailed information.

I have been using the solution for one and a half years.

The solution is stable.

The solution is scalable and has a large number of plugins that can help you scale it to your needs.

Aside from having to select the appropriate plugins the initial setup is straightforward.

The implementation was done in-house.

The solution is open source.

Before choosing the solution I evaluated TeamCity and GitHub Actions.

I give the solution eight out of ten.

The solution has several advantages over its competition because it doesn't require a license, is easy to integrate, and there are a lot of free resources and information available online.

I recommend the solution and suggest to anyone thinking about using it to first familiarize yourself with the plugins and know what it is you want to get out of the product before installing it.

There are over 2000 people in our organization and over 80 percent of our project use this solution.

The solution has readily available documentation and support that can be found online.

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.