firefox-android: Optimize gradle dependencies toolchain task on android-components
Categories
(Release Engineering :: General, enhancement)
Tracking
(firefox111 fixed)
| Tracking | Status | |
|---|---|---|
| firefox111 | --- | fixed |
People
(Reporter: jlorenzo, Assigned: jlorenzo)
References
()
Details
Attachments
(3 files)
In bug 1788606, we optimized gradle calls in the decision task. There's another gradle-based task that remains outstanding: the one that caches gradle dependencies. It was introduced in bug 1625126 and has regularly been called out as being too long, especially on Android-Components.
RELENG-736 suggests a solution: use a Nexus to proxy these dependencies. I think we shouldn't jump to this solution yet because of the lack of experience Mozilla has in monitoring such proxy. It's an easy target for supply-chain attacks.
Before, I think we should try something else: how about we split the toolchain tasks into smaller ones? Bug 1803141 made it easier to know what internal dependencies a gradle project has. So we can have 1 cache task per gradle project whose hash depends on its internal dependencies. This way, we don't wait on a single big task that caches all possibles deps.
I'll see how good this proposal is. I'd like to reduce the duration of this task before we migrate Fenix to the monorepo (bug 1803130). That duration delayed the migration by several hours on the day of the migration.
Comment 2•3 years ago
|
||
Comment 3•3 years ago
|
||
Johan, can we close this gradle bug?
You landed parts 1-9:
https://github.com/mozilla-mobile/firefox-android/commit/ecf523fb651dfe1ea4d4011f4e02129fa02a4eb6
...
https://github.com/mozilla-mobile/firefox-android/commit/366d63a61255bec91ed80be70b9a2a777d2b3883
| Assignee | ||
Comment 4•3 years ago
|
||
Sorry for the delay. I agree, let's close this bug as is. It definitely made things better on Android-Components. We're working on the Fenix migration to the monorepo and I see this task takes about an hour. We don't be able to optimize it the same way. Thus, I'll open a followup bug once we're done with the migration.
Comment 5•3 years ago
|
||
Comment 6•3 years ago
|
||
| Assignee | ||
Updated•2 years ago
|
| Assignee | ||
Comment 7•2 years ago
|
||
(In reply to Johan Lorenzo [:jlorenzo] from comment #4)
Thus, I'll open a followup bug once we're done with the migration.
Filed as bug 1820122.
| Comment hidden (collapsed) |
Description
•