Hi folks,

I'm working on a plan for transitioning Fennec builds to use Gradle in
automation (everywhere, really).  I've filed Bug 1254353 [1] to track this
effort.

Bug 1119520 [2] added an opt-in Gradle mozconfig option.  I've been using
it for new TaskCluster jobs, including our Unit testing job, so the
automation side of things is in reasonable shape.

I would like a few strategic testers to opt-in to Gradle building.  All
that you need to do is add

ac_add_options --with-gradle

to your mozconfig, then |mach configure| and |mach build| as usual.  You
should find that the moz.build system is only partially used; the Gradle
build kicks in to produce classes.dex; and |mach package| works as it did
before.

You should see no particular interaction between these moz.builds and your
Gradle/IDE builds, since they use different Gradle configurations.

It would be best if we had a few front-end developers (but not all!) and a
few platform developers (but again, not all!).  Please reply to this email
if you can help out for a few days.

Expect a transition plan in the next days and weeks, when I'll be asking
for your feedback and concerns.

Thanks!
Nick

[1] https://bugzilla.mozilla.org/show_bug.cgi?id=1254353
[2] https://bugzilla.mozilla.org/show_bug.cgi?id=1119520
_______________________________________________
mobile-firefox-dev mailing list
mobile-firefox-dev@mozilla.org
https://mail.mozilla.org/listinfo/mobile-firefox-dev

Reply via email to