We performed a comparison between Jenkins and Nx 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."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."
"There are a large number of plugins available for integration with third party systems."
"We have 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."
"I like that you can find a wide range of plugins for Jenkins."
"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."
"The automated elements are easy to use and you can put them into your server."
"With Jenkins, the pipeline will take your code from any versioning system like GitHub or Bitbucket. All the security scans can happen in one go and then all the tests also get run. You can just build one container in it and deploy it."
"We use Jenkins to automatically build Python binaries into several OS's i.e. OS X, Ubuntu, Windows 32-bit and Windows 64-bit."
"I really like Nx because it is easy to use and works right away."
"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."
"Centralized user management would be helpful."
"It could be cheaper."
"Developer documentation for plugins, plugin development, integrations: Sometimes it’s tricky to do pretty obvious things."
"Jenkins needs a faster deployment process."
"Jenkins takes a long time to create archive files."
"Jenkins is an open-source solution, and people tend to stay on the same version for a long time. When you look for an answer on Google, you often find something that doesn't relate to your implementation. The plugins are both the aspect of Jenkins and also one of the worst because the plugins can have different versions, so it's hard to figure out how to solve the problems."
"The support for the latest Java Runtime Environment should be improved."
"There are aspects of Nx that could be improved, particularly the desktop interface, which I find quite unappealing, mostly in black and white."
Jenkins is ranked 2nd in Build Automation with 83 reviews while Nx is ranked 16th in Build Automation with 1 review. Jenkins is rated 8.0, while Nx is rated 7.0. 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 Nx writes "Easy to use and works right away". Jenkins is most compared with GitLab, Bamboo, AWS CodePipeline, IBM Rational Build Forge and Tekton, whereas Nx is most compared with Bazel.
See our list of best Build Automation vendors.
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.