Jenkins Reviews

We use Jenkins for deploying with GenX and work on the pipeline too. We engage in many activities using both Jenkins and GenX. 

I love Jenkins. I like that you work on anything, and you make anything. Jenkins is very important for my team. I am satisfied with the product.

Jenkins can be improved, but it's difficult for me to explain. The initial setup could be more straightforward. If you connect Jenkins with bookings and lockouts, it can be challenging.

I have been using Jenkins for three years.

Jenkins is a stable product.

Jenkins is a scalable solution. We have ten people using this product right now.

Technical support was very good.

On a scale from one to five, I would give technical support a five.

Positive

The initial setup depends on the project and related activities.

I have implemented this solution myself, and I have also used a consultant on other occasions.

Jenkins is not expensive and reasonably priced.

I would recommend Jenkins to potential users. You can use Jenkins with other products and make anything you like. 

On a scale from one to ten, I would give Jenkins a ten.

The simplicity of Jenkins and the evolving ecosystem of Jenkins are most valuable. Today, you do not have to write a pipeline from scratch. The library functionality of Jenkins helps you to bring all those in ready-made, and you also get the best practices for them. That is a great feature of Jenkins, and that is why it is being used significantly.

Jenkins also helps you to be agnostic to cloud providers.

I would like to have an integrated dashboard on top of it and a better UX to look at. The dashboard could be better in terms of integration with other tools. We should be able to have a single pane of glass across all the tools that we use where Jenkins is the pipeline. This can be a very good upgrade to it.

I have been using this solution for about 10 years.

It is very stable.

It is highly scalable, and it can scale into different models.

In terms of its customers, I have worked with very big enterprises to small companies with about 100 people.

Jenkins is an open-source initiative. So, the support is more community-based. The community is great. I do not remember asking for help often because it is quite stable, but for any extensibility that can be built on it, the community is great. You can find lots of resources and helpful people.

It is definitely not complex. It might not be very easy for a newcomer, but it is in the easy to medium range to get started with.

As people are using it, they should come to the community and provide their input so that the community can grow better.

I would rate it an eight out of ten.

We use Jenkins for building our applications, deploying our applications, and some automation tasks.

We are using the open-source version and there is a lot of plugins and features that are available and it works on agents for free. In other solutions, it will cost extra to use them with the agent.

The UI of Jenkins could improve.

I have been using Jenkins for approximately six years.

Jenkins is stable. It provides all the required features for stability, such as backups.

Jenkins is scalable because it is open source and it integrates with other third-party vendor tools which are currently in the market, such as Microsoft Azure or Amazon AWS. It gets very well integrated with all the new tools, it doesn't remain isolated.

We have multiple projects that are using this solution and each project has multiple users. In one project we could have 50 users or in another 10 users are using it.

We didn't face any issues to escalate to Jenkins for technical help.

We have previously used Bamboo. I use both Jenkins and Bamboo per our project requirements. Jenkins is more suitable for commercial projects and is more scalable and flexible as compared to other tools because its core focus is on integrating and updating automatically.

The initial setup of Jenkins was straightforward. It's very lightweight and it only requires Java on your system as a requirement.

We did the implementation of the solution ourselves with our team.

We are using the free version of Jenkins. There is not a license required to use the solution because it is open-source.

My advice to others is to explore Jenkins well and it is integrated with the scripting site. Teams should explore the scripting part of the Jenkins because everybody's nowadays is writing pipeline as a code for automating their operations. They should try to utilize the new feature provided to them, such as pipeline as a code. 

It does not matter what solution they are using, such as Microsoft Azure DevOps or Amazon AWS DevOps, Jenkins will integrate with other solutions. They should try and use Jenkins even if they're using some other tool.

I rate Jenkins an eight out of ten.

I'm a software engineer at a large bank. 

Jenkins increases our performance efficiency and saves us a significant amount of time.

We were initially SQL-based until we moved to object-oriented language and started hosting our code on Jenkins. The main benefit for us is the automation and we've done it in such a way that you only need to run one build that triggers itself and the rest of the builds downstream. We're moving most of our builds over to Jenkins because of all the automation it offers. It has a good interface, is reliable, and saves time. 

I think the logs could be improved so that anyone using the build for the first time gets a better view as to how it's performing, what the data is, and what processing is occurring. I'd like to see errors displayed differently. It currently takes an effort to find out where an error is and I think the error message and logging which is not jargon-based, is something I would like to see included.

I've been using this solution for two years. 

This is a stable solution. We are a team of 25 people, all working with Jenkins in some way or other, whether it's the finance data adapter or the magnet platform, which is totally Java-based and uses Jenkins. We have mainly software engineers and a few business analysts on the team. We also have a maintenance team that deals with any issues that come up.

I have tried the partial plugin for Jenkins which we use for regression and analysis and it works well. 

Our technical support is all in-house. All software deployment information is available online and it's pretty easy to follow. 

We have a license contract with Jenkins. 

Jenkins is a great solution if you're looking at automation because it reduces manual work and improves performance. If you deploy it on cloud, then performance is improved further. It's worth reducing dependency by targeting a one-build solution for Jenkins. 

I rate the solution eight out of 10. 

Most obvious: Having builds and test tasks triggered on commit helps not to break the product.

From my own experience:

We significantly reduced build times of large projects (more than 80k lines of Scala code) using build time on Jenkins as a time sample. It reduced the developer write-test-commit cycle time, and increased productivity.

Integration with GitLab reduced time used for code reviews. Jenkins posted build state and code quality reports into the merge request.

Simplified build scripts: Organisation started to integrate Pipelines as a part of a build, and built a library of common functions. It simplified and made our build scripts more readable. 

Automation of chores like deployment, frequent manual tasks (like running scripts on test and production systems) reduced the time used and the number of errors made by engineers, freeing them to do meaningful work instead.

• Configuration management: It is so easy to configure a Jenkins instance. Migrate configuration to a new environment just by copying XML files and setting up new nodes.
• Programmable pipelines: In recent versions, Jenkins has a Groovy Sandbox where build scripts execute. I have never seen that powerful a tool in CI solutions yet. On other platforms you can use shell scripts, but Jenkins' solution is much better in terms of readability and portability. And given that you can create your own libraries for the Jenkins Pipelines, it becomes much more powerful and DRYer, simplifying work of DevOps and build engineers.
• Brand new Blue Ocean UI: Jenkins used to have a pretty outdated UI. Now, you can use the Blue Ocean plugin to make it nice, clean, and modern-looking. Also, it has very good integration with Pipelines (basically it is built to use Pipelines).

UI: Jenkins relies on the old version of interface for configuration management.

Developer documentation for plugins, plugin development, integrations: Sometimes it’s tricky to do pretty obvious things.

Rarely. I can remember only one time we lost our build info after upgrading Jenkins, somewhere around the 1.6xx versions.

Sometimes you have Jenkins restarting because of OOM errors.

No scalability issues. I used to have up to five worker nodes with one master, and it did not produce any slowdowns. I have never had bigger deployments.

I have never used technical support directly. The community, documentation, issue tracker, are pretty good, though not ideal.

TeamCity - It’s pretty limited in build runners, mostly targeting enterprise tech (Java, MS Stack, mobile apps) and the price is quite high.

Buildkite - An okay solution, but builds are shell scripts in general. It’s hard to maintain them. Also, I had weird issues with SCM integrations and Github.

GitLab CI - It’s coupled with GitLab too tightly. It’s pretty difficult to configure. It’s slow and requires a lot of resources to run.

As for me, I just start to use it. It runs builds, unless you need something more complicated.

Setup of commonly used plugins is very straightforward, but it can be more difficult to get it running with exotic technologies. Still, it’s much easier than with other solutions.

I used the free OSS version all the time. It was enough for all my needs.

I was always choosing between Jenkins, TeamCity, Buildkite, and Bamboo. Most recently, hosted solutions like Codeship and Travis CI added to the list.

For business needs, Jenkins is the most relevant choice because it can be self-hosted, the price is good, it’s robust, and requires almost no effort for maintenance.

For open source projects, Travis CI is standard.

I like it very much, and I'm actively promoting it on my network.

Take your time to get used to the management flows of the application and builds. Jenkins is very powerful when you know how to cook it.

We use this solution to build, test, and then deploy new software to the FTP server.

This solution has improved our organization with how much time it saves when coding.

We really appreciate that this solution is plug and play. When coding in the version control system, this product completes the build process automatically.

We would like to see the addition of mobile simulators support to this solution, as part of its open-source offering. We currently have to carry out manual testing for these platforms.

We have worked with this solution for around four years.

We have found the stability of this solution to be good.

Due to the lack of mobile simulators, we have not scaled this solution.

We have not had to contact the technical support team; the official documentation provided has resolved any issues we came across.

We found the initial setup of this solution to be okay. The setup isn't complicated, but there is some step by step documentation provided that will need to be read and followed during the process.

The deployment of the product took one or two days initially, and only took one person to action.

We carried out implementation and deployment of this product using our in-house team.

This is an open-source solution for the basic features. However, if an organization wishes to include specific functionality, outside of the basic package, there are extra costs involved.

We previously trialed an AWS-based product. However, it was complex to use and conflicted with some of our existing software.

We highly recommend this solution for web development. However, for mobile development, it may be better for organizations to consider other options.

I would rate this solution a five out of ten.

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.

We use the solution for the whole automation cycle for the deployments. We are using Jenkins and pipelines for once commits or push commits on Bitbucket or directories. Jenkins is listening for those changes and is applying (or triggered by) the repository changes to deploy and run the test cases, automate test cases, and deploy them on servers for the deployment, testing, or production.

It's open-source and free to use.

The learning curve for Jenkins is not a big deal. It has a lot of community posts and support. 

The initial setup is simple. 

We have found the solution to be stable.

It is my understanding that the solution can scale. 

Jenkins is on-premise (on our infrastructure) and Bitbucket or Azure directories are on the cloud. Therefore, triggering from the repositories to the on-premise, Jenkins is not applicable. We are trying to reach them now, and we are currently using a plan or a process to listen to the repositories every once in a while to know if there are no new changes applied. It triggers the automation for the deployment and the running test cases, and therefore it may take two minutes or three minutes to have the deployment done after the latest commit. This is due to the fact that we are using on-premise Jenkins for on-premise deployment, yet have the repositories on the cloud. There is no way for the cloud repositories to trigger Jenkins. We are trying to research now how to have the Jenkins over a public IP, so the repositories can trigger it.

We have been dealing with Jenkins for around three years now.

The product is stable. There are no bugs or glitches. It doesn't crash or freeze. It's reliable. 

Although it is my understanding the solution can scale, we don't have much information about scalability for the Jenkins. We didn't investigate scaling yet.

We tend to search for solutions online. I've never reached out to technical support. I rely more on the community. 

It's pretty straightforward to set up the product. The DevOps team just took around two weeks or three weeks for the first deployment, for automation for the first deployment using Jenkins. It fulfilled our requirements. DevOps is not a target by itself, DevOps is an operation to remove any pain areas, or time-consuming tasks, or to automate it to have it in seconds. It fulfills our requirements.

The product is open-source.

For the development environment, we are using the on-premise infrastructure. For some customers we are also using on-premise; for other customers, we are using the cloud.

We have branches in Egypt and branches in Dubai that are using Jenkins for the whole automation process and we're really enjoying using it.

I would recommend the solution to others.

I'd give it a rating of seven out of ten.