(In reply to Mihai Tabara [:mtabara]⌚️GMT from comment #4)
First of all, please bear with me - just to make sure we're all on the same page:
- by "removing Fennec" we mean cleaning its traces from central, beta and release and keeping it in ESR branch until we have a resolution on its future relationship with Fenix. Correct?
Correct. I wouldn't expect to uplift anything at all, so this would be "deleting tons of stuff from m-c" and then having it ride the trains.
- IIUC, we now have
ship_geckoview in central, beta and release where we build, sign and push the artifacts under https://maven.mozilla.org/?prefix=maven2/org/mozilla/geckoview/. By
the Fennec APK will no longer be "the package you specifically talk about no longer building this
public/build/target.apk (e.g. in this task). Correct?
Correct, not building
target.apk. My try builds are green now but I'll follow up with
Ns tasks to see what happens. Presumably we need to remove the
Ns tasks (and potentially other tasks) since there'll be no Fennec APK to sign shortly.
If so, I don't think we actually need any replacement, nor any form of packaging. In shipping geckoview, we both sign + beetmove individual files and we no longer use any maven.zip or alike, as you mentioned too. So not building that
target.apk will presuambly have no effects in Releng ecosystem as it is. But the contrary, we can perform some cleanup which is great.
OK: it sounds like there's no releng need for a package, since we're doing much, much more flexible things for the Maven artifacts already. That's great!
LATER EDIT: seems like we actually do sign the
apk with the
autograph_apk_fennec_sha1 format but we never actually ship those in the maven.m.o .
That's true, but I think we have some capability to ship a Fennec APK from m-c to Google Play. That's disabled right now ('cuz esr68 is servicing those APKs) but the capability should be removed from m-c as well. Perhaps that is the cleanup you are referring to?
The beetmover declarative artifacts (such as this) stands proof as there's no trace of
target.apk around there. I strongly suspect this was carried over while we did some migration to Autograph earlier this year.