Closed Bug 1150537 Opened 5 years ago Closed 5 years ago
Document the differences between the raw engineering builds and the ones published
Per bug 1150009, we discovered the differences between the engineering build you have by simply running ./build.sh and the engineering builds we publish (like on pub.mozilla.org or pvtbuilds). Let's document that.
Started https://developer.mozilla.org/en-US/Firefox_OS/Building/Building_an_engineering_build_like_the_ones_publis. Still some variables to explain.
Assignee: nobody → jlorenzo
QA Whiteboard: [fxosqa-auto-s13+]
The QA team was wondering why we have all these variables set on the build slaves. Do you have an idea, Nick? If not, do you know who can help us? Thanks!
Chris David Mills moved the doc page to https://developer.mozilla.org/en-US/Firefox_OS/Building which makes sense. I've deleted the page I created yesterday. I also updated the meaning of every variable after some investigation. There is one that I'm not sure of: MOZ_AUTOMATION=1. This is a Gecko variable. Martijn, do you know about this variable?
Sorry, I don't know anything about this variable.
Hi Chris, Per bug 946691 comment 3, the MOZ_AUTOMATION variable seems to have been introduced at that time. I'm not sure what it changes from TINDERBOX_OUTPUT. Is it something you might be able to help me figure out? Thanks !
It's meant to be a more general variable than TINDERBOX_OUTPUT, and is to be used as a hint to the build system that the build is running under automation.
Ok, so if I understand correctly, neither Gecko or Gaia would be affected by this variable. I've cleared that variable on the MDN page.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.