We performed a comparison between Concourse for VMware Tanzu, Jenkins, and JFrog Pipeline 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.
"We never experienced any problems with scalability."
"Jenkins has been instrumental in automating our build and deployment processes."
"The most valuable feature of Jenkins is its continuous deployment. We can deploy to multi-cluster and multi-regions in the cloud."
"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."
"Different types of jobs, such as Pipeline, Build, Freestyle, Maven, etc."
"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."
"Jenkins has excellent task planning features."
"When we have manual tasks, we have to depend on multiple technical teams. With Jenkins, we can bring all the technologies together by the click of a button. We can see results without having to depend on different teams. Jenkins makes life easy for the database and DevOps teams."
"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."
"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."
"The platform has some amazing features and the integration option makes it very simple to plug with any of our favorite tools."
"I would like to see additional support for things outside of Cloud Foundry."
"It would be better if there were an option to remove its Java dependency. This would make it more compatible with other software, and it could be much better. At present, we have to depend on Java whenever we want to deploy agents."
"Jenkins is an old product, and we encounter performance issues and slow response. Also, some of the plugins are not stable."
"I think an integrated help button, that respected the context of the change/work in hand, would be a worthwhile improvement."
"The UI of Jenkins could improve."
"The upgrades need improvement."
"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."
"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."
"The learning curve is quite steep at the moment."
"They could work on reducing the number of permissions required while using Bitbucket."
Earn 20 points
