Heroku vs Jenkins comparison

"The solution's most valuable feature is the auto maintenance of databases."

"I like the tool's scalability, CLI, and dashboards."

"The most valuable feature of Heroku is the continuous integration and applications it provides."

"Valuable for us was the fast deployment. This means the time to market is improved without pain for developers."

"We use Heroku to run generic data. We also use it for our customer development environment. It helps us to build and test websites."

"The product is stable."

"It is easy to deploy applications, and we don't need to bother about software updates on the server. We don't need to bother about machines, servers, and hardware. We only need to care about the system and functionality that we need or want to develop. They take care of everything else. It provides high availability. It is a pretty good solution that provides everything that we need. It has everything that we need to run our applications. We have many different applications, and we generate three million bills for a company in Brazil. We see more than a billion requests per day in another application. Everything works just fine, and it is very good."

"The platform is very Node.js-friendly, which is something that is important to us."

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

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

"It's very easy to learn."

"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 has a lot of built-in packages and tools."

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

"Has enabled full automation of the company."

"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 pricing could be improved because scaling the database becomes costly."

"They could flesh out some of their analytics a little more."

"Heroku doesn't support Docker images on the CI infrastructure."

"Heroku should increase its slug size limits."

"We would like to be notified when something goes wrong in the process. When something is not working, we should get an alert."

"We have to do daily restarts of some processes, which is annoying, and the support for custom CI could be better."

"Heroku had an authentication problem a few months ago, but they solved it."

"The tool's configuration is complex."

"Jenkins takes a long time to create archive files."

"Jenkins could simplify the user interface a little bit because it sometimes creates too many features cramped in the UI."

"The solution's UI can use a facelift and the logs can use more detailed information."

"A more user-friendly UI for creating pipelines would be helpful."

"It can be improved by including automated mobile reporting integrations."

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

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

"Developer documentation for plugins, plugin development, integrations: Sometimes it’s tricky to do pretty obvious things."

"Its price is very good."

"The tool is free."

"The price of Heroku could be less expensive."

"There is a standard fee for a processing unit, they call them "dynos," and then you pay for add-ons."

"I rate the tool's pricing a three out of ten."

"We use the tool's open-source version which is free. There is an enterprise version which is expensive but comes with better support."

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

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

"It could be cheaper because there are many solutions available in the market. We are paying yearly."

"There is no cost. It is open source."

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

"Jenkins is an open-source tool."

"Jenkins is an open-source platform."