activate mozilla-b2g18 branch

RESOLVED FIXED

Status

Release Engineering
General
RESOLVED FIXED
6 years ago
a year ago

People

(Reporter: hwine, Assigned: hwine)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [re-b2g])

Attachments

(1 attachment)

(Assignee)

Description

6 years ago
Pulling this into separate bug, as there is new coordination needed to ensure the gecko.git repo stays correct. Once we get the go, the steps are:

1. stop gecko-18 updating to git.m.o:releases/gecko.git
2. complete all hg cutover work
3. switch gecko-18 processing to the new hg branch
4. restart gecko-18 updating

The time sensitive steps are the ordering of #1 & #2 - just like with merge/uplift days we have to stop the updating of gecko.git BEFORE making any changes in hg.
(Assignee)

Comment 1

6 years ago
There will also be changes in buildbot-configs/mozilla/b2g_configs - see notes in file.
(Assignee)

Updated

6 years ago
Assignee: nobody → hwine
Status: NEW → ASSIGNED
(Assignee)

Comment 2

6 years ago
Created attachment 691441 [details] [diff] [review]
config changes to move unagi-stable from m-b to m-b2g18

passes test-masters.sh
Attachment #691441 - Flags: review?(aki)

Updated

6 years ago
Attachment #691441 - Flags: review?(aki) → review+
(Assignee)

Comment 3

6 years ago
Comment on attachment 691441 [details] [diff] [review]
config changes to move unagi-stable from m-b to m-b2g18

http://hg.mozilla.org/build/buildbot-configs/rev/f59ae4af5197
Attachment #691441 - Flags: checked-in+

Comment 4

6 years ago
This is in production.
Comment on attachment 691441 [details] [diff] [review]
config changes to move unagi-stable from m-b to m-b2g18

>diff --git a/mozilla/b2g_config.py b/mozilla/b2g_config.py
> BRANCHES['mozilla-beta']['platforms']['unagi']['mozharness_config']['extra_args'] = ['--target', 'unagi', '--config', 'b2g/releng-beta.py', '--gaia-languages-file', 'shared/resources/languages-dev.json']

I think we need to change the --config here, or perhaps this goes away if we're disabling b2g on mozilla-beta. Rail would know for sure.
Never mind, bug 820949 removed all of mozilla-beta.
(Assignee)

Comment 7

6 years ago
see also confirmation in bug 821078
Status: ASSIGNED → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
Component: Tools → General
Product: Release Engineering → Release Engineering
You need to log in before you can comment on or make changes to this bug.