Closed Bug 820594 Opened 12 years ago Closed 12 years ago

generate "engineer/marionette-enabled" b2g builds

Categories

(Release Engineering :: General, defect, P3)

x86
Gonk (Firefox OS)
defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: joduinn, Assigned: catlee)

References

Details

Attachments

(2 files, 2 obsolete files)

This "new" build type was discovered last week during the transition from Ateam builds to RelEg builds. Its now added to https://etherpad.mozilla.org/b2g-builds. All other build types have been transitioned. jgriffin: assigning to you first. Please post instructions on how to generate these builds here, and then please reassign this to catlee.
The instructions are the same as for existing otoro/nightly builds, except that you omit the VARIANT=user environment variable when running build.sh. You can explicitly specify VARIANT=eng if you'd like, but it defaults to this, so you can just omit it entirely.
Assignee: jgriffin → catlee
s/otoro\/nightly/otoro\/unagi/
On what frequency should these engineering builds be generated? On which branches should they be built?
To achieve parity with what's on releases.mozilla.com currently, we'd only need builds against mozilla-b2g18 and nightly gaia, once nightly. However, with the per-commit update testing we plan on standing up with unagi's soon, it would be really helpful to have these builds made per-commit to mozilla-b2g18. There's no need to generate these builds on other gecko branches, AFAIK.
Priority: -- → P3
This will override the gecko config. Also, PEP8 FTW.
Attachment #693001 - Flags: review?(rail)
Comment on attachment 693001 [details] [diff] [review] support --variant for b2g_build.py lgtm
Attachment #693001 - Flags: review?(rail) → review+
jgriffin, is there any need to publish manifests for these builds?
Flags: needinfo?(jgriffin)
(In reply to Chris AtLee [:catlee] from comment #7) > jgriffin, is there any need to publish manifests for these builds? No there is not.
Flags: needinfo?(jgriffin)
I ended up needing a new config file for this since we need a different upload suffix and slightly different set of actions (I'm assuming we don't need to upload manifests for these builds)
Attachment #693001 - Attachment is obsolete: true
Attachment #694013 - Flags: review?(rail)
Attachment #694219 - Flags: review?(rail)
Comment on attachment 694013 [details] [diff] [review] support --variant for b2g_build.py Review of attachment 694013 [details] [diff] [review]: ----------------------------------------------------------------- Looks good in overall. Just a couple of nits. ::: scripts/b2g_build.py @@ +273,5 @@ > + dirs = self.query_abs_dirs() > + gecko_config = self.load_gecko_config() > + env = self.query_env() > + env.update(gecko_config.get('env', {})) > + if self.config.get('variant') is not None: "is not None" can be dropped to improve readability. @@ +276,5 @@ > + env.update(gecko_config.get('env', {})) > + if self.config.get('variant') is not None: > + v = str(self.config['variant']) > + env['VARIANT'] = v > + if self.config['ccache']: maybe self.config.get('ccache') to be safer?
Attachment #694013 - Flags: review?(rail) → review+
Comment on attachment 694219 [details] [diff] [review] set up unagi_eng on mozilla-b2g18 Looks like this one is identical to the first patch. A wrong patch maybe?
Attachment #694219 - Flags: review?(rail)
oops!
Attachment #694219 - Attachment is obsolete: true
Attachment #694474 - Flags: review?(rail)
Attachment #694474 - Flags: review?(rail) → review+
Attachment #694013 - Flags: checked-in+
Attachment #694474 - Flags: checked-in+
Depends on: 823737
This is in production.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: