Jenkins Reviews

We use Jenkins for integrated reporting. We have different projects that require coaching, gate configuration, and clone effects. We build packages, deploy, and upload-pack eights. We start at software changes and follow the process through to final testing and eventually launching. 

Jenkins has excellent task planning features. 

We have a variety of examples in our organization.  We have security configurations that we would like to isolate across our platform. It is not always easy to control the permissions for each user. There are cases where I do not want everyone to have access to the technical aspect of a job or even that the job exists.

I have been using Jenkins now for ten years.

We have found Jenkins to be very stable.

I believe Jenkins is scalable. We have over two hundred users. We have plans to increase this number.

We have not used technical support. We just Google, from the internet. Most of the time we can solve it on our side.

The initial set-up is easy for a single-link system. For more complicated systems it is not easy. As a product, Jenkins has been in the top five for more than five years, so that is not a problem.  

We did an in-house implementation. We have an incremental process for deployment. We also have a complete patent for official patent deployment. We have two patents, one for development and one for official relief. We have an integration team that is responsible for these patents.

Jenkins has a free licensing program.

Jenkins is the most popular automation engine in the world. There are other options, but fewer users. There are some other choices in the market but Jenkins is definitely number one. I would rate Jenkins an eight out of ten.

We use Jenkins for management purposes.

The most valuable features of Jenkins are creating builds, and connecting them with Sonar for Sonar analysis. Additionally, we connect it with other vulnerability tools, such as WhiteSource which is useful.

Jenkins could improve the integration with other platforms.

I have been using Jenkins for approximately two years.

Jenkins is stable.

I have found Jenkins to be scalable.

We have different teams within our company using this solution with different types of setups. We have approximately 25 users using the solution.

I have not contacted the support from Jenkins.

The initial implementation of Jenkins is simple.

The installation of Jenkins is done by our team.

I would recommend this solution to others.

I rate Jenkins an eight out of 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 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.

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.

My primary use case is as a CI pipeline in order to deploy onto the GCP. This allows us to push any changes into the master brand.

The major benefit of using Jenkins is that it's a very secure way of deploying something to the cloud. It has also improved the drawbacks of manual deployments by making them more robust and secure, and it helps the user avoid mistakes because all the checks are there in one script which can be used every time.

The most valuable feature of Jenkins is the logs it provides - these are very helpful in understanding error conditions so we can see where the problem lies and go in and check it. Another useful feature is the GUI, which estimates how long a particular model will need to be executed. It's also very easy to understand for newcomers. 

One area for improvement would be the UI, which currently looks quite outdated and requires the user to go through too many steps. In the next release, I would like to have the ability to use the command prompt to navigate between repositories and to enable features.

There are some minor bugs with this solution, but overall the stability is ok.

Jenkins is very scalable.

The initial deployment is easy if you are familiar with script creation - a person who is unfamiliar with this might have difficulties with setup. It can be set up by a single person in four to five hours.

I would rate this solution as eight 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.

Jenkins is used for triggering my test automation. I use Selenium WebDriver for test automation.

The most valuable features of Jenkins are the ease of use and the information about how to use the features is readily available on the internet. Additionally, with the solution, I can use other reporting tools, such as Flow.

Jenkins could improve by adding the ability to edit test automation and make time planning better because it is difficult. It should be easier to do.

I have been using Jenkins for three years.

Jenkins has been stable in my usage. However, I have had colleagues say they have had stability problems. They experienced these problems after six months to a year of use.

We have approximately four engineers using Jenkins and they use it as needed. It could be weekly or monthly.

There is not any support for the solution since it is open-source. However, you can find all the information needed online.

For triggering I use Jenkins, but for local systems, I used Selenium WebDriver. Additionally, I have used Cypress.

The initial setup of Jenkins is in the medium-difficult range.

Jenkins is a free solution, it is open source.

I rate Jenkins a seven out of ten.