HockeyApp vs Jenkins

Overview

HockeyApp

Stacks164

Followers158

Votes38

Jenkins

Stacks59.2K

Followers50.4K

Votes2.2K

GitHub Stars24.6K

Forks9.2K

HockeyApp vs Jenkins: What are the differences?

Deployment Automation: Jenkins is primarily a continuous integration and continuous deployment tool that automates the build and deploy processes. It allows for seamless integration and testing of code changes, ensuring efficient deployment workflows. In contrast, HockeyApp is focused on mobile app distribution, beta testing, and crash reporting, targeting the specific needs of mobile app developers.
Customizability: Jenkins offers extensive customization options through plugins, allowing users to tailor their CI/CD pipeline to suit specific project requirements. On the other hand, HockeyApp provides a more streamlined approach with pre-defined features for mobile app development, limiting the customization capabilities compared to Jenkins.
Platform Support: Jenkins is platform agnostic, capable of running on various operating systems, offering flexibility to users, enabling them to work in environments of their choice. In contrast, HockeyApp is predominantly geared towards mobile app development, supporting platforms like iOS, Android, and Windows, catering specifically to the mobile app industry.
Community Support: Jenkins boasts a large and active open-source community, supporting users with extensive documentation, forums, and plugins. This vast community ensures that users can find solutions to problems, share best practices, and continuously enhance their Jenkins experience. On the other hand, HockeyApp, owned by Microsoft, has a more focused community primarily centered around mobile app development.
Monitoring and Analytics: Jenkins provides basic monitoring capabilities to track build statuses, performance metrics, and notifications for failed builds. In comparison, HockeyApp offers more detailed analytics and crash reporting specifically tailored for mobile apps, providing deeper insights into app performance and user behavior.
Integration with Other Tools: Jenkins offers seamless integration with a wide range of tools and technologies, making it versatile and adaptable to different development environments. HockeyApp, while providing integration options, is more optimized for integration with Microsoft's development ecosystem, such as Visual Studio and Azure DevOps.

In Summary, Jenkins and HockeyApp differ significantly in their focus, customizability, platform support, community, monitoring capabilities, and integration options.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs

CLI (Node.js)

Manual

Advice on HockeyApp, Jenkins

Balaramesh

Apr 20, 2020

Needs adviceon

Azure Pipelines

.NET

Jenkins

We are currently using Azure Pipelines for continous integration. Our applications are developed witn .NET framework. But when we look at the online Jenkins is the most widely used tool for continous integration. Can you please give me the advice which one is best to use for my case Azure pipeline or jenkins.

663k views663k

Comments

StackShare

Apr 17, 2019

Needs advice

From a StackShare Community member: "Currently we use Travis CI and have optimized it as much as we can so our builds are fairly quick. Our boss is all about redundancy so we are looking for another solution to fall back on in case Travis goes down and/or jacks prices way up (they were recently acquired). Could someone recommend which CI we should go with and if they have time, an explanation of how they're different?"

529k views529k

Comments

Tatiana

Nov 16, 2019

Decided

Jenkins is a pretty flexible, complete tool. Especially I love the possibility to configure jobs as a code with Jenkins pipelines.

CircleCI is well suited for small projects where the main task is to run continuous integration as quickly as possible. Travis CI is recommended primarily for open-source projects that need to be tested in different environments.

And for something a bit larger I prefer to use Jenkins because it is possible to make serious system configuration thereby different plugins. In Jenkins, I can change almost anything. But if you want to start the CI chain as soon as possible, Jenkins may not be the right choice.

734k views734k

Comments

Detailed Comparison

HockeyApp	Jenkins
HockeyApp is the best way to collect live crash reports, get feedback from your users, distribute your betas, and analyze your test coverage.	In a nutshell Jenkins CI is the leading open-source continuous integration server. Built with Java, it provides over 300 plugins to support building and testing virtually any project.
Crash Reports- HockeyApp offers the most reliable and complete crash reporting for beta and App Store versions using open source frameworks. Providing full server-side symbolication with class names, methods, line numbers, and automatic grouping of similar crash reports.;Feedback- HockeyApp allows you to communicate with your customers. Users can create a support request, post an idea, or discuss a problem right from within the app.;Distribution- Upload your beta versions to HockeyApp and distribute them to your beta testers. Integrate our open-source SDK and your app will automatically be able to detect updates and offer the updates right within the app.Analytics- By integrating our SDK into your app, you'll get advanced metrics to get a better overview of the testing for your app. See which devices were tested, which testers used the app for how long, and which language was tested.	Easy installation;Easy configuration;Change set support;Permanent links;RSS/E-mail/IM Integration;After-the-fact tagging;JUnit/TestNG test reporting;Distributed builds;File fingerprinting;Plugin Support
Statistics
GitHub Stars -	GitHub Stars 24.6K
GitHub Forks -	GitHub Forks 9.2K
Stacks 164	Stacks 59.2K
Followers 158	Followers 50.4K
Votes 38	Votes 2.2K
Pros & Cons
Pros 17 Crash analytics 11 Cross-platform 5 Mobile application distribution 2 JIRA Integration 2 Open source	Pros 523 Hosted internally 469 Free open source 318 Great to build, deploy or launch anything async 243 Tons of integrations 211 Rich set of plugins with good documentation Cons 13 Workarounds needed for basic requirements 10 Groovy with cumbersome syntax 8 Plugins compatibility issues 7 Lack of support 7 Limited abilities with declarative pipelines
Integrations
Hipmob	No integrations available

What are some alternatives to HockeyApp, Jenkins?

Travis CI

Free for open source projects, our CI environment provides multiple runtimes (e.g. Node.js or PHP versions), data stores and so on. Because of this, hosting your project on travis-ci.com means you can effortlessly test your library or applications against multiple runtimes and data stores without even having all of them installed locally.

Codeship

Codeship runs your automated tests and configured deployment when you push to your repository. It takes care of managing and scaling the infrastructure so that you are able to test and release more frequently and get faster feedback for building the product your users need.

CircleCI

Continuous integration and delivery platform helps software teams rapidly release code with confidence by automating the build, test, and deploy process. Offers a modern software development platform that lets teams ramp.

TeamCity

TeamCity is a user-friendly continuous integration (CI) server for professional developers, build engineers, and DevOps. It is trivial to setup and absolutely free for small teams and open source projects.

Drone.io

Drone is a hosted continuous integration service. It enables you to conveniently set up projects to automatically build, test, and deploy as you make changes to your code. Drone integrates seamlessly with Github, Bitbucket and Google Code as well as third party services such as Heroku, Dotcloud, Google AppEngine and more.

wercker

Wercker is a CI/CD developer automation platform designed for Microservices & Container Architecture.

GoCD

GoCD is an open source continuous delivery server created by ThoughtWorks. GoCD offers business a first-class build and deployment engine for complete control and visibility.

TestFlight

With TestFlight, developers simply upload a build, and the testers can install it directly from their device, over the air.

Shippable

Shippable is a SaaS platform that lets you easily add Continuous Integration/Deployment to your Github and BitBucket repositories. It is lightweight, super simple to setup, and runs your builds and tests faster than any other service.

Buildkite

CI and build automation tool that combines the power of your own build infrastructure with the convenience of a managed, centralized web UI. Used by Shopify, Basecamp, Digital Ocean, Venmo, Cochlear, Bugsnag and more.

Related Comparisons

HockeyApp vs Jenkins: What are the differences?

Deployment Automation: Jenkins is primarily a continuous integration and continuous deployment tool that automates the build and deploy processes. It allows for seamless integration and testing of code changes, ensuring efficient deployment workflows. In contrast, HockeyApp is focused on mobile app distribution, beta testing, and crash reporting, targeting the specific needs of mobile app developers.
Customizability: Jenkins offers extensive customization options through plugins, allowing users to tailor their CI/CD pipeline to suit specific project requirements. On the other hand, HockeyApp provides a more streamlined approach with pre-defined features for mobile app development, limiting the customization capabilities compared to Jenkins.
Platform Support: Jenkins is platform agnostic, capable of running on various operating systems, offering flexibility to users, enabling them to work in environments of their choice. In contrast, HockeyApp is predominantly geared towards mobile app development, supporting platforms like iOS, Android, and Windows, catering specifically to the mobile app industry.
Community Support: Jenkins boasts a large and active open-source community, supporting users with extensive documentation, forums, and plugins. This vast community ensures that users can find solutions to problems, share best practices, and continuously enhance their Jenkins experience. On the other hand, HockeyApp, owned by Microsoft, has a more focused community primarily centered around mobile app development.
Monitoring and Analytics: Jenkins provides basic monitoring capabilities to track build statuses, performance metrics, and notifications for failed builds. In comparison, HockeyApp offers more detailed analytics and crash reporting specifically tailored for mobile apps, providing deeper insights into app performance and user behavior.
Integration with Other Tools: Jenkins offers seamless integration with a wide range of tools and technologies, making it versatile and adaptable to different development environments. HockeyApp, while providing integration options, is more optimized for integration with Microsoft's development ecosystem, such as Visual Studio and Azure DevOps.

In Summary, Jenkins and HockeyApp differ significantly in their focus, customizability, platform support, community, monitoring capabilities, and integration options.

HockeyApp vs Jenkins

Overview