Jenkins vs Nx comparison

"Jenkins is stable, user-friendly, and helps with continuous integration. As of today, I can't see any tool that's better than Jenkins."

"Jenkins is very easy to use."

"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."

"Jenkins integrates with multiple tools like Bitbucket and makes life easier. We don't have to write a lot of code since a lot of libraries are available."

"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 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."

"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."

"The most valuable feature of Jenkins is its continuous deployment. We can deploy to multi-cluster and multi-regions in the cloud."

"I really like Nx because it is easy to use and works right away."

"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."

"There are a lot of things that they can try to improvise. They can reduce a lot of configurations. It is currently supporting Groovy for scripting. It would be really good if it can be improvised for Python because, for most of the automation, we have Python as a script. It would be good if can also support Python. We have a lot of Android builds. These Android builds can be a part of Jenkins. It can have some plug-ins or configurations for Android builds. There should also be some internal matrix to check the performance. We also want to have more REST API support, which is currently not much in Jenkins. We are not able to get more information about running Jenkins. More REST API support should be provided."

"The user interface could be improved, and its reporting capabilities need enhancement. The plugins could be more effective."

"The support for the latest Java Runtime Environment should be improved."

"There is no way for the cloud repositories to trigger Jenkins."

"Jenkins is an old product, and we encounter performance issues and slow response. Also, some of the plugins are not stable."

"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."

"There are aspects of Nx that could be improved, particularly the desktop interface, which I find quite unappealing, mostly in black and white."

"The open-source version is free, but small companies would not be able to afford the cloud-based version."

"Jenkins is a free solution, it is open source."

"Jenkins is an open-source tool."

"The pricing for Jenkins is free."

"The solution is open source."

"In our company, we do pay for the licensing of the solution."

"​It is free.​"

"Jenkins is open-source, so it is free."