[Dependency Analysis] Add Android Gradle Plugin #148
Conversation
FYI: This commit adds a previous version of the plugin (1.28.0) and not the latest version (1.32.0). This is because the latest version gets stuck during the 'computeActualUsage' phase and increases the build time of the 'buildHealth' task by as much as five times (5x). For more info see: Stuck in computeActualUsageDebug for many minutes #1186 (https://github.com/autonomousapps/ dependency-analysis-gradle-plugin/issues/1186)
FYI: With this configuration only the 'debug' variant (build type) for for all modules is going to be included, with the rest of the variants ignored.
FYI: 1. This job will be then used by 'buildkite-ci' and configured as a 'buildkite_pipeline_schedule' with a weekly frequently. 2. This job will also notify on the android-core-notifs slack channel on a build failure.
…ndroid into build/dependency-analysis-android-gradle-plugin
| common_params: | ||
| # Common plugin settings to use with the `plugins` key. | ||
| - &common_plugins | ||
| - automattic/a8c-ci-toolkit#2.15.0 |
There was a problem hiding this comment.
Can we use the newest version?
| - automattic/a8c-ci-toolkit#2.15.0 | |
| - automattic/a8c-ci-toolkit#3.4.2 |
There was a problem hiding this comment.
I would love to do that @wzieba but I really don't want to make a change that can potentially block this PR (ie. failing CI, etc), me not knowing exactly what the diff between the 2 version are. 🤷
Can I maybe do that on a separate PR next week, and do that for all these 6 libraries I have been (Login, Media Picker) and will be touching next week (Aztec, About, Tracks)? 🙏
There was a problem hiding this comment.
What works best for you - the only breaking difference is related nvm installation, but if you prefer to do this in a separate PR, it's ok to me too 👍
There was a problem hiding this comment.
Cool, great, I've noted this down and will create separate PRs for each library I have been or will be touching next week. 🗒️
the only breaking difference is related nvm installation
👍
Project Thread: paaHJt-6yU-p2
Required By: BuildkiteCI#473
Depends On:
This PR adds the dependency analysis Android Gradle plugin to this project, for dependency analysis purposes.
Description
For now, only the main
buildHealthtask is going to be utilized and produce data once every week on CI (see this commit and this PR). Amongst other, this data will include the following:projectCount)unusedCount)undeclaredCount)misDeclaredCount)compileOnlyCount)runtimeOnlyCount)Afterward, this data will get collected from CI and uploaded to our Apps Metrics infrastructure, for visualization and alerting purposes.
Testing Steps
./gradlew buildHealthtask and verify that under the root levelbuild/reports/dependency-analysisfolder you get the below 2 reports both, in JSON and text format:build-health-report.jsonbuild-health-report.txtNew Build🟢 CI button for UtilsAndroid, test this standalone dependency analysis job (see form below). Then:/meta-datato that CI build's URL (example) will give you one extra meta-data, thepipeline_fileone, with a value ofschedules/dependency-analysis.yml(see screenshot below):build/reports/dependency-analysis/build-health-report.jsonbuild/reports/dependency-analysis/build-health-report.txthttps://api.buildkite.com/v2/organizations/automattic/pipelines/wordpress-utils-android/builds?meta_data[pipeline_file]=schedules/dependency-analysis.yml