perf-org-5krepos / libhockey

Python wrapper around the Hockey App API

This project has been deprecated

Due to the immenent switch from Hockey to App Center, this project has been deprecated. Minor updates may still be made, but these should not be counted on in any way. No pull requests will be accepted at this point. Any issues are unlikely to be addressed.

libhockey

libhockey is a wrapper around the Hockey App REST API. It's aim is to be a simple and easy to use as possible.

It doesn't cover every single API, but does the basics. Feel free to open an issue or a pull request for API support.

Getting started

Just add the following and you are ready to go:

import libhockey

client = libhockey.HockeyClient(access_token="...")

Examples

Listing all versions of an app

for version in client.versions.generate_all("[app id]"):
    print(version.download_url)

Uploading a build

download_link = client.versions.upload("/path/to/app.ipa", "Release notes go here")

Find new crashes in a build

current_crashes = client.crashes.groups_for_version("[app id]", "[current version id]")
previous_crashes = client.crashes.groups_for_version("[app id]", "[previous version id]")
new_crashes = list(set(current_crashes) - set(previous_crashes))

for crash in new_crashes:
    print(f"({crash.number_of_crashes}) {crash.crash_file} - {crash.crash_class}:{crash.crash_method}")

Contributing

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.microsoft.com.

When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.