Closed Bug 1691101 Opened 3 years ago Closed 3 years ago

Remove jcenter/bintray from android-gradle-dependencies task

Categories

(GeckoView :: General, task, P1)

Unspecified
All

Tracking

(firefox88 fixed)

RESOLVED FIXED
88 Branch
Tracking Status
firefox88 --- fixed

People

(Reporter: nalexander, Assigned: owlish)

References

Details

(Whiteboard: [geckoview:m88][fenix:p1])

Attachments

(1 file)

It's a sad day: as of May 1, 2021 jcenter/bintray will disappear. See https://jfrog.com/blog/into-the-sunset-bintray-jcenter-gocenter-and-chartcenter/.

The android-gradle-dependencies task fetches dependencies from jcenter/bintray: https://searchfox.org/mozilla-central/rev/40205f1b55f1ba8a26fcbd362c20d843e8718a87/mobile/android/gradle.configure#439.

I don't know what is actually coming from jcenter/bintray. That is the first step to quantify what needs to be done. The best way to determine that is to fetch the archive from the toolchain task and take a look at the downloaded repositories. Given a list of things we're fetching from jcenter, I know of no way to automatically determine where to start fetching those dependencies from; it might be a github searching exercise. (Hopefully all our dependencies publish somewhere other than jcenter!)

With that list in hand, the next step will be to (potentially) upgrade the Nexus version used in the a-g-d task (since what we are consuming is ancient) and to hack up the existing https://searchfox.org/mozilla-central/source/taskcluster/scripts/misc/android-gradle-dependencies/nexus.xml to not reference jcenter and to reference some other, hopefully small, set of external repositories.

Stefan: this appears likely to impact android-components as well: https://searchfox.org/mozilla-mobile/source/android-components/taskcluster/scripts/toolchain/android-gradle-dependencies/nexus.xml. Can you redirect this to the right people to address for that project? Thanks!

Flags: needinfo?(sarentz)

We have a meta in the A-C product tracking the various project changes that are needed across the set of apps we support. https://github.com/mozilla-mobile/android-components/issues/9603

(In reply to Kevin Brosnan [:kbrosnan] from comment #2)

We have a meta in the A-C product tracking the various project changes that are needed across the set of apps we support. https://github.com/mozilla-mobile/android-components/issues/9603

Beautiful -- thanks, Kevin. This reminds me that we may be able to depend on Maven Central instead of jcenter and more or less Go On With Life.

Priority: -- → P2
Whiteboard: [geckoview:m88]
Whiteboard: [geckoview:m88] → [geckoview:m88][fenix:p1]
Priority: P2 → P1
Rank: 3
Assignee: nobody → bugzeeeeee
Pushed by istorozhko@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/9456d2f7812f
Migrate from jcenter in android builds r=geckoview-reviewers,nalexander,agi
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Target Milestone: --- → 88 Branch
See Also: → 1697852
Flags: needinfo?(sarentz)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: