Re: The future of files-based metadata in moz.build files

I'll only add that moving this to a separate file set would have the benefit of significantly simplifying the moz.build reading code, which is quite complex and somewhat slow. I don't have a profile offhand that points to Files() as a bottleneck, but it could become a concern if we were to continue

Re: Python configure: status and discussing improvements

On Wed, Aug 17, 2016 at 2:29 AM, Mike Hommey wrote: > On Tue, Aug 16, 2016 at 03:51:51PM +0900, Mike Hommey wrote: > > Here's my own list of things that I find suboptimal, with suggestions > > when I have some. > > - I'm trying to enforce separation of concerns between generic things, > > app-s

Re: Python configure: status and discussing improvements

On Mon, Aug 15, 2016 at 11:51 PM, Mike Hommey wrote: > Hi, > > It's almost been 6 months since bug 1250294 landed, initiating the long > and slow move off autoconf. > > Where are we, 6 months later? While there hasn't been constant progress > in the migration (we've all been busy with other thing

Re: RFC: Moving from confvars.sh to moz.configure

e you'd > have browser-specific sections and android-specific sections all > interspersed with each other. So I would vote for option 1 at the moment, > unless there's a more concrete example of a problem we'd avoid with 2. > > -Mike > > On Tue, May 3, 2016 a

RFC: Moving from confvars.sh to moz.configure

We're moving some things currently defined in various confvars.sh files to Python configure (moz.configure), and have reached a point where feedback would be helpful, as we are replacing a relatively longstanding thing, and many are likely to interact with these options in the future. The competin

Artifact builds are now available to Git users

Git is now supported for artifact based builds for those using git-cinnabar . The MDN page has been updated to reflect this -- other than using git-cinnaba

Re: Metrics for builds in automation

This seems to overlap a lot with what we're submitting to perfherder, except that perfherder has individual build steps (compile, package, etc...), while this has some different visualizations. These seem to be optimized for different use cases, but will end up charting a lot of the same data. For

Re: [ann] Firefox "artifact builds" for Mac OS X

Support for test plugins landed on inbound earlier this afternoon. This required modifying rules for installation paths, so some cached archives will be invalidated by this change. Please `rm ~/.mozbuild/package-frontend/*.processed.jar` after pulling to avoid build bustage as a result of this cha