Jenkins Reviews

I primarily use Jenkins to deploy APIs for microservices, creating pipelines and providing the source code link.

Jenkins helps to maintain continuous integration whenever we make changes in the code and to deploy the code whenever we do any check-ins.

The onboarding of Jenkins should be smoother, and it should have more pipelines available as it's deployed on many different servers. We should be able to do minimal configuration changes and deploy our API from multiple regions like AWS, GCP, or virtual environments like VM.

I've been using Jenkins for six years.

Jenkins works perfectly well - we've never faced any outages or issues with it.

The initial setup isn't difficult.

We implemented using an in-house team.

Jenkins is stable, user-friendly, and helps with continuous integration. As of today, I can't see any tool that's better than Jenkins. If you have very few APIs which can be deployed manually, I wouldn't recommend Jenkins. However, I would recommend it for those with multiple APIs and many clients, who are doing code changes on a daily basis. I would give Jenkins a rating of seven 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.

The primary use cases include manifest generation and publishing modules.

Whenever we do releases, it goes to Jenkins to publish a version of the application and the version being released. Jenkins plays a big role in this process.

GitHub linking is pretty good. We have a deployment application where we can run our tests and add various variables to be passed as assertions to those tests. This is pretty fluid with Jenkins.

It is a stable solution and is generally scalable.

Sometimes, random errors of metadata are not there, which causes delays. These are essentially gaps in the information being passed to the job. This could be reduced and would save a lot of time.

Jenkins runs in correlation with GitHub but can only run one job at a time. Also, that job is a pre-selected job. So, if you select a particular job, then that job would run for all your pull requests. It would be amazing if for pull request one, for example, I could do build one, and for pull request two, I could do build two.

I've been working with Jenkins for two years.

It's quite stable and pretty reliable.

To a large extent, it is scalable; after that, some manual interference is required at certain points.

In our company, everybody works with Jenkins, so we have more than 10,000-20,000 users.

I am satisfied with the technical support services.

I would recommend Jenkins and would rate it at nine on a scale from one to ten.

Our company is in development. We provide development solutions for our clients. 

Jenkins is a code repository. We use it for the code repository.

It is easy to use.

It could be cheaper.

I have been using this solution for four or five years.

 It is stable.

It is scalable. Currently, we have around 67 or 70 users. We have plans to increase its usage.

I didn't interact with them. Other people take care of this.

We used GitHub.

It is easy to install.

There were other developers who installed it. For deployment and maintenance, we have a team in which everyone has a role. They do their own thing.

It could be cheaper because there are many solutions available in the market. We are paying yearly.

I would recommend this solution. I would rate Jenkins a seven out of ten.

We use it as a pipeline and for the whole development life-cycle. We even built the whole infrastructure and use it with cloud formation. In AWS, we use it with cloud formation when we build the infrastructure as a code.

It's fantastic. I like it, and I have no problem with it. It's very small, easy to use, and very straightforward.

It would help if they offered more integrations.

I have been using Jenkins for about two years.

It's very flexible, and you can add a lot of applications there to develop and more. We have about five guys using it, but we also have a very big development team with over 50 developers.

I installed it a couple of times, and the initial setup was easy. I didn't have any difficulties when it came to deployment.

I installed Jenkins by myself.

I would recommend this solution, but it depends on the project. It has a lot of support, and it's been in the market for a long time. Many big organizations also use it.

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

In this solution, you can write scripts and put job parameters in them with time and dates when to activate. We can create a web book that is automatically configured. The automated elements are easy to use and you can put them into your server. Additionally, there are plenty of plugins available. You can use the plugins to push your code into a target or container. There are many features available in this solution.

The scriptwriting process could be improved in this solution in the future.

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

The solution is stable.

We have not had any issues with scaling the solution.

I have previously used Bamboo and it is really easy to use, user-friendly, and the UI well designed. The control output of Bamboo is highly interactive for the user. 

I have also previously used Sonar but it is a lot different than this solution and Bamboo.

The solution is one of the lowest costs compared to competitors.

When selecting a solution I would advise checking their budget, the volume size they are performing, and what full-stack they are performing on. Based on this information, they can better determine what solution is best for them. If they have a low budget this solution would be great for them. 

I rate Jenkins an eight out of ten.

We use a Hybrid cloud. We are deploying internally on our own servers i.e. our virtual servers in Microsoft Azure. We have 6 engineers using Jenkins Primer. It is only for internal use. We use it for the automation pipeline in our development of software. It compiles and moves the software to deployment in the Microsoft Azure cloud. We also use Jenkins to generate documentation for all the software.

The documentation could be more friendly, and more examples of how to use it. This would make for easier implementation in several environments.

Jenkins is very stable.

We read all the documentation. We also took online training on the internet, which included videos and training tasks. It takes some study and learning, but we don't experience any technical problems.

It took a few weeks for the initial installation of the Jenkins server to set up the development virtual pipeline.

The implementation was undertaken by developers and other internal staff.

I would rate Jenkins 9 out of 10.

We used it for continuous integration and had its latest version in the previous organization. I am now using Azure DevOps.

It is open source, flexible, scalable, and easy to use. It is easy to maintain for the administrator. It is a continuous integration tool, and its enterprise version is quite mature.

It has good integrations and plug-ins. Azure DevOps can also be integrated with Jenkins.

Its schedule builds need improvement. It should have scheduling features in the platform rather than using external plug-ins.

I used this solution for around one and a half years.

It is scalable. We had five users of this solution.

We were using another solution from Automic.

It is easy and quick to install. It took us less than an hour.

I installed it. You just need a single resource for its deployment and maintenance.

There is no cost. It is open source.

I would recommend this solution. It is good for small companies but not for big companies. It has a good interface and was easy to customize. We were also using another plug-in to enhance the user interface.

I would rate Jenkins a seven out of ten.