android-automation-tools
android-automation-tools copied to clipboard
mozilla-mobile
Tools for automating tasks in Android projects
Two repositories are now injected. Plugin version is bumped to 0.3
### Pull Request checklist - [x] This PR includes thorough **tests** or an explanation of why it does not - [x] This PR includes a **CHANGELOG entry** or does not...
Severin [mentioned in my PR landing this on FFES](https://github.com/mozilla-mobile/firefox-echo-show/pull/263#discussion_r263610354) that it might be clearer where these tasks come from if we namespace them. While most gradle plugins don't seem to...
Ideally, we'd be using TaskCluster, or similar to publish new releases. See #31 for setting up CI.
Sometimes malicious packages with similar names can be hosted on different packaging sites: https://blog.autsoft.hu/a-confusing-dependency/ We should make sure the dependencies are listed in an optimal order like: - mozilla maven...
In #32, we get find the release tasks by checking that they start with `assemble` and end in `Release`: this is pretty hacky. The Android gradle plugin might have more...
We have some plugin code in our ac repository. Maybe it should live here instead? **GVNightlyVersionVerifierPlugin**: This plugin can automatically update a local GeckoView dependency (currently only Nightly and currently...
Mike has started the work to create a Mozilla Gradle plugin. Let's add a helper to setup the Mozilla repository - so that we can just do: ```Groovy repositories {...
The configurations are basically duplicated for components, focus, and TV. fwiw, on Fire TV, I noticed that there appears to be a coverage task we don't use: ```sh ./gradlew -Pcoverage...
We have some code in Focus (and future apps) to generate a version code for release builds. How can we share this code? Could this be a gradle plugin? https://github.com/mozilla-mobile/focus-android/blob/master/tools/gradle/versionCode.gradle
Metadata
Owner
Metadata
Tools for automating tasks in Android projects