1541820 - Implement a gradle plugin for Glean

Status: RESOLVED FIXED

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

Description

[Alessio Placitelli [:Dexter]]

When using gradle's "offline" mode, building products using glean fails with this error:

FAILURE: Build failed with an exception.

• Where:

Build file '/Users/XXX/src/reference-browser/app/build.gradle' line: 261

• What went wrong:

A problem occurred evaluating project ':app'.

Could not get resource 'https://github.com/mozilla-mobile/android-components/raw/master/components/service/glean/scripts/sdk_generator.gradle'.
Could not HEAD 'https://github.com/mozilla-mobile/android-components/raw/master/components/service/glean/scripts/sdk_generator.gradle'.
> github.com: nodename nor servname provided, or not known

Comment 3

[Michael Droettboom [:mdroettboom]]

Some questions as I come back to this work:

• I see that Fenix now has both an android components version and a mozilla-glean version, which I presume must be kept in sync. We can make gradle plugin releases in tandem with glean-core releases, so we can use the same mozilla-glean version number for both glean-core and the gradle plugin. However, what happens if android-components and mozilla-glean are not a matched pair (which doesn't necessarily mean the same version number...)?

• I'm not aware of any projects linking to the sdk_generator.gradle file in the mozilla/glean repo (only the one in android-components). I think it makes sense to keep it like that -- let's migrate all the projects from the sdk_generator.gradle in a-c to the plugin in mozilla/glean in one step. Agree?

Comment 4

[Michael Droettboom [:mdroettboom]]

Attachment: GitHub Pull Request

Comment 5

[Jan-Erik Rediger [:janerik] (Away 2026-04-02 - 2026-04-10)]

Agree, but this Android stuff and what repos to pull in where seems like :dexter-territory.

Comment 6

[Alessio Placitelli [:Dexter]]

(In reply to Michael Droettboom [:mdroettboom] from comment #3)

Some questions as I come back to this work:

• I see that Fenix now has both an android components version and a mozilla-glean version, which I presume must be kept in sync.

Yes, bug 1588098 tracks the work to address that.

We can make gradle plugin releases in tandem with glean-core releases, so we can use the same mozilla-glean version number for both glean-core and the gradle plugin. However, what happens if android-components and mozilla-glean are not a matched pair (which doesn't necessarily mean the same version number...)?

Yes, this is a good potential solution! As long as there's no mismatch between the version of mozilla-glean used in a-c and the one that the gradle-plugin makes the product use, we should be fine. Otherwise... we'll potentially crash in tests :)

• I'm not aware of any projects linking to the sdk_generator.gradle file in the mozilla/glean repo (only the one in android-components). I think it makes sense to keep it like that -- let's migrate all the projects from the sdk_generator.gradle in a-c to the plugin in mozilla/glean in one step. Agree?

Yes, I agree :)

Comment 7

[Michael Droettboom [:mdroettboom]]

It feels really good to close this one.