Opened 5 years ago

Last modified 3 years ago

#2791 new change

[Meta] Automated builds and releases — at Version 2

Reported by: rjeschke Assignee:
Priority: P3 Milestone:
Module: Adblock-Browser-for-Android Keywords: 2015q4
Cc: Blocked By:
Blocking: Platform: Adblock Browser for Android
Ready: no Confidential: no
Tester: Unknown Verified working: no
Review URL(s):

Description (last modified by rjeschke)

We need to set up a release mozconfig and appropriate build environment.

Things to notice here are:

  • look into Mozilla's buildbot configurations located here.
  • look into /mobile/android/config/mozconfigs for Mozilla's release configuration and adapt to our needs
  • we probably need to build different Fennec APKs for ARM, x86 and for API<11
  • we do not need the crash reporter currently, so we also need ac_add_options --disable-crashreporter
  • additional flags for the build configuration could also contain (see #2564):
    # Permission reduction
    ac_add_options --disable-websms-backend
    ac_add_options --disable-webrtc
    ac_add_options --disable-webapp-runtime
    ac_add_options --disable-mozril-geoloc
    
  • check if we need an Adjust SDK token or if we can disable this

We can possibly create release mozconfigs and check them in into the repository. Best practise IMO would be to create a adblockbrowser subfolder in /mobile/android/config/mozconfigs and mimic Mozilla's behaviour in there (more or less).

Change History (2)

comment:1 Changed 5 years ago by rjeschke

  • Description modified (diff)

comment:2 Changed 5 years ago by rjeschke

  • Description modified (diff)
Note: See TracTickets for help on using tickets.