We performed a comparison between Jenkins and Microsoft Azure based on real PeerSpot user reviews.
Find out what your peers are saying about GitLab, Jenkins, Amazon Web Services (AWS) and others in Build Automation."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."
"Jenkins is the most widely used development tool, so there are many plugins and it's easy to integrate. There is a large user base to provide community support, which I find very valuable. If I need to find a better way to do something, I can always get help from the community. Automation is about thinking outside of the box, and other users are constantly adding new plugins."
"The most valuable feature of the solution is its integration between different tools."
"It has a lot of community posts and support."
"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 most valuable features are Jenkins Pipelines for ALM and full Deploy Cycle."
"We use Jenkins to automatically build Python binaries into several OS's i.e. OS X, Ubuntu, Windows 32-bit and Windows 64-bit."
"Jenkins allows us to automate deployment, so I no longer have to do it manually. That's the primary use case. The other advantage of Jenkins is that it's open source. It was free for me to download and install. It's a product that's been in use for many years, so I can find a lot of support online for any issues that I may encounter while configuring anything for a given use case."
"It's stable, easy to use, reliable, and cheap."
"The solution is useful for handling large amounts of data."
"The most valuable feature is the instant availability of resources."
"The data factory feature."
"It was very user-friendly when setting up the virtual machines and console. It was an easy task for my team to create virtual servers and start replications."
"There are a lot of things that we like about it. It is very easy to provision and configure. It is flexible and scalable."
"The most valuable feature is the possibility of using Microsoft and non-Microsoft services on one environment."
"The stability has been excellent."
"It can be improved by including automated mobile reporting integrations."
"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."
"The UI must be more user-friendly."
"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."
"The documentation could be more friendly, and more examples of how to use it."
"The enterprise version is less stable than the open-source version."
"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."
"This solution would be improved with the inclusion of an Artifactory (Universal artifact repository manager)."
"Integration with more platforms needs improvement."
"They're already doing quite a bit. I'm not unsatisfied with anything that they're doing right now. They can maybe make the transitions a little smoother and improve its pricing. The pricing for the end-user packages is a bit high."
"It would be ideal if they could reduce costs a bit. Right now, we find the product to be expensive."
"I would like to see better policy-based management and everything related to security management could have been better integrated."
"The solution’s learning curve could be improved."
"The design of the platform is not so easy to navigate. It's not very user-friendly."
"In my opinion, what could be improved is making the actual costs more predictable. It is very difficult to estimate the cost or the budget you are going to need to run your environment in Azure Cloud. You have to be a specialist to understand how you will be charged, which constantly changes."
"Microsoft Azure can improve by adding more features for virtual machines, such as tier virtual machines."
Jenkins is ranked 2nd in Build Automation with 83 reviews while Microsoft Azure is ranked 1st in Infrastructure as a Service Clouds (IaaS) with 299 reviews. Jenkins is rated 8.0, while Microsoft Azure is rated 8.4. The top reviewer of Jenkins writes "A highly-scalable and stable solution that reduces deployment time and produces a significant return on investment". On the other hand, the top reviewer of Microsoft Azure writes "Promotes clear, logical structures preventing impractical configurations and offers seamless integration ". Jenkins is most compared with GitLab, Bamboo, AWS CodePipeline and IBM Rational Build Forge, whereas Microsoft Azure is most compared with Google Firebase, Amazon AWS, Oracle Cloud Infrastructure (OCI), Pivotal Cloud Foundry and SAP Cloud Platform.
We monitor all Build Automation reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
