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, Google and others in Build Automation."Very easy to understand for newcomers."
"We used it for all continuous integration parts, like automation testing, deployment, etc."
"It has a lot of community posts and support."
"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."
"We can schedule anything with Jenkins, which is useful for deployment or anything that requires scheduling. It also has multiple plugins we can use for Maven, JUnit, etc."
"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."
"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 is stable, user-friendly, and helps with continuous integration. As of today, I can't see any tool that's better than Jenkins."
"The solution is very stable for Windows setups."
"It's very scalable. We can scale up to 80-85% without issues."
"We didn't have any problems setting it up."
"There are many useful features. We use web apps, so instead of starting a web server, we just have machines running some web services. This was helpful for us in terms of the scalability of the application. We also use Active Directory for authentication and some services for the data backup. It is a very good and reliable solution. It was easy to implement this solution. It fits very well into our plans and covers our needs to provide infrastructure in the cloud. The portal to configure new resources is very easy, and it is very easy to allocate new resources."
"The initial setup is simple."
"We are using Microsoft Azure because our organization uses a lot of Microsoft solutions. We have used Microsoft technology for a long time and we have internal engineers with great capability that understand the technology. This is why Azure is the best for us."
"I like the ExpressRoute because that makes it easy to configure connectivity to Azure-hosted services."
"With the Azure solution, you can get more value from your cloud investment no matter what your future goals are. It depends on your level of familiarity with the cloud you are using or with your computing. Azure helps you with every stage of the cloud."
"We cannot change the ownership of any directory or file or any kind of directory."
"Upgrading and maintaining plugins can be painful, as sometimes upgrading a plugin can break functionality of another plugin that a job is dependent on."
"Jenkins could improve by allowing more scripting languages. We need to use Groovy scripting and it is difficult to debug and it is not ideal for creating file scripts. We tried to search for assistance but we did not find much help."
"Jenkins could have better cloud functionality. Currently, we are using the existing legacy model, but we are moving toward the cloud, so it would be great if they could improve in that area. In the future, I would like more cloud features and related training materials, like a video tutorial."
"UI is quite outdated."
"This solution would be improved with the inclusion of an Artifactory (Universal artifact repository manager)."
"Jenkins needs a faster deployment process."
"The onboarding of Jenkins should be smoother, and it should have more pipelines available as it's deployed on many different servers."
"As compared to AWS, Azure can improve its functionality. In terms of the feature list, it is still lacking a bit as compared to AWS. AWS supports lots of types of operating systems, which Azure is still catching up with. Azure is mainly focused on the Windows system, and it is not yet there in terms of integration with other operating systems like Linux, Unix. Azure is slowly catching up."
"From a security perspective, there is always something that can be improved as we serve our customers."
"I would prefer Microsoft Azure to increase the free trial, then developers can take advantage, and it could increase their sales."
"The solution could use mutual segmentation for servers. It would be ideal if you could constitute something like five or 15 groups among the groups of different computers inside Azure."
"The interface is not easy to use. I'd like to see them develop a better interface, more graphical information about the resource and the consumer."
"The only thing is regarding the management of multi-cloud environments. That's not really possible."
"Microsoft Azure could improve by having the availability be 100%. Which is difficult, but not impossible."
"At this point, the latency is too high to use Azure in our production environment."
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, IBM Rational Build Forge and JFrog Pipeline, whereas Microsoft Azure is most compared with Google Firebase, Oracle Cloud Infrastructure (OCI), Amazon AWS, 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.