Project Thread: paaHJt-6yU-p2
Required By: BuildkiteCI#478
Depends On:
[x] #1083
This PR adds the dependency analysis Android Gradle plugin to this project, for dependency analysis purposes.
Description
For now, only the main buildHealth task 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:
Number of modules (projectCount)
Unused dependencies which should be removed (unusedCount)
Transitive dependencies which should be declared directly (undeclaredCount)
Existing dependencies which should be modified to be as indicated (misDeclaredCount)
Dependencies which could be compile-only (compileOnlyCount)
Dependencies which should be removed or changed to runtime-only (runtimeOnlyCount)
Afterward, this data will get collected from CI and uploaded to our Apps Metrics infrastructure, for visualization and alerting purposes.
Testing Steps
Local: Run the ./gradlew buildHealth task and verify that under the root level build/reports/dependency-analysis folder you get the below 2 reports both, in JSON and text format:
build-health-report.json
build-health-report.txt
CI: Using the New Build 🟢 CI button for AztecAndroid, test this standalone dependency analysis job (see form below). Then:
When CI starts, make sure that adding /meta-data to that CI build's URL (example) will give you one extra meta-data, the pipeline_file one, with a value of schedules/dependency-analysis.yml (see screenshot below):
When CI completes, make sure that the below 2 CI artifacts are available both, in JSON and text format:
REST: Using the Buildkite's REST API you could query for this type of builds, using the meta-data query parameter, and see that the result is the expect one. Use this query: https://api.buildkite.com/v2/organizations/automattic/pipelines/azteceditor-android/builds?meta_data[pipeline_file]=schedules/dependency-analysis.yml
Project Thread: paaHJt-6yU-p2 Required By: BuildkiteCI#478 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 AztecAndroid, 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/azteceditor-android/builds?meta_data[pipeline_file]=schedules/dependency-analysis.yml