1436577 - Publish GeckoView Beta and Release builds on archive.mozilla.org

Status: RESOLVED DUPLICATE of bug 1433198

(Release Engineering :: General, enhancement)

Description

[Chris Peterson [:cpeterson]]

In bug 1433198, we want to publish a Maven repo pointing to the latest GeckoView builds.

IIUC, we need to publish the GeckoView AAR files (e.g. geckoview-default-armeabi-v7a-60.0a1.aar) alongside the Fennec APKs on ftp like:

https://ftp.mozilla.org/pub/mobile/releases/58.0/android-aarch64/en-US/

https://ftp.mozilla.org/pub/mobile/nightly/latest-mozilla-central-android-aarch64/en-US/

The Maven repo from bug 1433198 can point to the GeckoView AARs on ftp or someplace like S3, but we will still want the AARs archived on ftp.

Comment 1

[Chris Peterson [:cpeterson]]

catlee, can you please help us with this bug?

In Maven bug 1433198 comment 2, you mentioned pointing to GeckoView's Taskcluster artifacts on the Nightly S3 bucket. Is that bucket overwritten by each Nightly build? Since other Mozilla products will be consuming GeckoView builds, we will want to archive our builds on ftp.mozilla.org for posterity. Pointing the Maven repo to ftp instead of S3 might be less work and this bug would be a prerequisite for setting up the Maven repo.

Comment 2

[Chris AtLee [:catlee]]

"ftp" is a deprecated name for what is now https://archive.mozilla.org. That is backed by an S3 bucket with a CDN in front of it.

It sounds like the AAR file could be published beside the maven repo? They would show up in directories like:

https://archive.mozilla.org/pub/mobile/nightly/latest-mozilla-central-android-aarch64/en-US/
https://archive.mozilla.org/pub/mobile/nightly/2018/02/2018-02-07-10-03-49-mozilla-central-android-aarch64/en-US/

The files in the "latest" directories get overwritten every time a nightly build is done.

Comment 3

[Chris AtLee [:catlee]]

Are the AAR files currently produced by the build? Do they need any kind of signing before they're published alongside the fennec APK?

Comment 4

[Chris Peterson [:cpeterson]]

(In reply to Chris AtLee [:catlee] from comment #2)
> "ftp" is a deprecated name for what is now https://archive.mozilla.org. That
> is backed by an S3 bucket with a CDN in front of it.

Good to know. I'll stop saying ftp. :)


> It sounds like the AAR file could be published beside the maven repo? They
> would show up in directories like:
> 
> https://archive.mozilla.org/pub/mobile/nightly/latest-mozilla-central-
> android-aarch64/en-US/
> https://archive.mozilla.org/pub/mobile/nightly/2018/02/2018-02-07-10-03-49-
> mozilla-central-android-aarch64/en-US/

@snorp?

I think I misunderstood how the Maven repo works. I thought we needed to host one centralized Maven repo that would point to the latest GeckoView builds, but it looks like GeckoView consumers can use the stable URLs that we already have like https://archive.mozilla.org/pub/mobile/nightly/latest-mozilla-central-android-aarch64/en-US.


(In reply to Chris AtLee [:catlee] from comment #3)
> Are the AAR files currently produced by the build?

Yes, there is a geckoview-default-armeabi-v7a-60.0a1.aar file in the Taskcluster artifacts you linked to in Maven bug 1433198 comment 2:

https://tools.taskcluster.net/groups/aeV9uG2cSmmwv50M1_WaYw/tasks/fn_4xGUVRQCZXf6XXywX1w/runs/0/artifacts


> Do they need any kind of signing before they're published alongside the fennec APK?

@snorp?

Comment 5

[James Willcox (:snorp) ([e-mail]) (he/him)]

(In reply to Chris Peterson [:cpeterson] from comment #0)
Yeah, I think there is some misunderstanding here. Bug 1433198 requests the Maven repo, which also includes the AARs, be hosted on "ftp" (or https://archive.mozilla.org). We do indeed want this to go in the "-latest" directory next to the Nightly Fennec builds. I don't think we need anything additional from this bug, unless I'm missing something.

Comment 6

[Chris Peterson [:cpeterson]]

James and I discussed this bug on Slack. I didn't realize that the GeckoView AAR was part of the maven repo, so publishing the maven repo into the mobile/nightly/latest-mozilla-central-android-* directories (in bug 1433198) will automatically archive the maven repo (and GeckoView AAR) into the dated nightly and beta directories.