1569184 - Automate the listing of a-c dependencies for powering probe-scraper

Status: RESOLVED WONTFIX

(Data Platform and Tools :: Glean: SDK, enhancement, P3)

Description

[Alessio Placitelli [:Dexter]]

For Android products built off Android Components, the probe-scraper needs to know which components make up an application, given that each single component might be collecting Glean metrics.

This is currently done as follows:

1. the repositories.yaml file declares a list of components and the location for their related metrics.yaml file;
2. the same file also reports dependencies_url for applications, which points to a text file including a list of component names that make up the application.

As of today, having the file for (2) requires adding a TaskCluster task to the product CI in order to make that file available. This imposes a dependency on the developers of the application itself, which need to setup TaskCluster in addition to let probe-scraper know about their application.

A potential enhancement would be to make the probe-scraper download the applications repos and issue the gradle command to get the components, in a Docker container.

Comment 1

[Jan-Erik Rediger [:janerik]]

We need to investigate: how hard will this be to accomplish?

Comment 2

[Michael Droettboom [:mdroettboom]]

After discussion in the Glean "end-to-end" meeting today, it was decided to replace all automatic dependency management with manual lists with some automatic alerts to help us find things we may have missed. Closing this in favor of 1577253