JFrog Pipeline vs Jenkins comparison

"The most valuable feature of the solution is its integration between different tools."

"Jenkins has excellent task planning features."

"Distributed execution of build and test jobs."

"We significantly reduced build times of large projects (more than 80k lines of Scala code) using build time on Jenkins as a time sample. It reduced the developer write-test-commit cycle time, and increased productivity."

"The automated elements are easy to use and you can put them into your server."

"The initial setup is simple."

"Also, the ability to customize these plugins is valuable. Its user-friendliness stands out, especially in its user interface which allows easy installation and configuration."

"The most valuable aspect of Jenkins is pipeline customization. Jenkins provides a declarative pipeline as well as a scripted pipeline. The scripted pipeline uses a programming language. You can customize it to your needs, so we use Jenkins because other solutions like Travis and Spinnaker don't allow much customization."

"The platform has some amazing features and the integration option makes it very simple to plug with any of our favorite tools."

"Testing against multiple run times, versions, and environments is a plus point with the additional pipelines making it more interesting to see what is happening across your development process in a single pane of glass."

"This solution would be improved with the inclusion of an Artifactory (Universal artifact repository manager)."

"UI is quite outdated."

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

"Jenkins could improve the integration with other platforms."

"Some kind of SaaS product would be helpful in providing organizational structure."

"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 UI must be more user-friendly."

"I sometimes face a bottleneck when installing the plugins on an offline machine. Mapping the dependencies and then installing the correct sequence of dependencies is a nightmare, and it took me two days to do it."

"They could work on reducing the number of permissions required while using Bitbucket."

"The pricing for Jenkins is free."

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

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

"Jenkins is an open-source tool."

"It's free software with a big community behind it, which is very good."

"It is an open source."

"This is an open-source solution for the basic features. However, if an organization wishes to include specific functionality, outside of the basic package, there are extra costs involved."

"We are using the freeware version of Jenkins."

"The pricing is the cheapest compared to the other platforms out there."