Closed Bug 913992 Opened 7 years ago Closed 7 years ago

[Tracking bug] automation support for B2G v1.2.0

Categories

(Release Engineering :: General, defect)

x86
All
defect
Not set

Tracking

(firefox26 fixed, b2g-v1.2 fixed)

RESOLVED FIXED
Tracking Status
firefox26 --- fixed
b2g-v1.2 --- fixed

People

(Reporter: joduinn, Assigned: catlee)

References

Details

(Whiteboard: [b2g])

Attachments

(4 files, 1 obsolete file)

We'll be needing automation support for b2g v1.2 soon, so that v1.3 work can land on master. Let's get the branches, repos, etc. created ahead of time. Note: to start with, v1.2 should be kept closed to developer-checkins until we get the official word.

For reference, bug#850481 tracked setup for v1.1.0, and bug#877787 tracked setup for v1.1.0hd.
Assignee: nobody → catlee
Whiteboard: [b2g]
So, I think all we need to do here is make sure that b2g builds/tests get activated on aurora as part of the merging process next week.
Also required:
- 1.2 branches in gaia, b2g-manifests
- update config.json in mozilla-aurora after the merge to point to new 1.2 branches
- bump version number for m-c/master builds
We also need to make sure the new v1.2 branch, and any l10n repos, are replicated/mirrored over to git.m.o, like we've done for earlier B2G releases.
OS: Mac OS X → All
Depends on: 915249
For the next cycle, 1.2 development will be happening on mozilla-aurora and 1.3 work will begin on mozilla-central. We need to make sure all B2G builds and tests currently active on mozilla-central are enabled on aurora next week.
Blocks: 842868
For merge day - bump mozilla-central to 1.3.0 and add mozilla-aurora as 1.2.0
Attachment #803546 - Flags: review?(aki)
Comment on attachment 803546 [details] [diff] [review]
bump b2g versions

I don't think we're converting aurora in gecko.git atm; I think we'll have to make that change for 1.2.0 to work.
Attachment #803546 - Flags: review?(aki) → review+
Depends on: 915585
Depends on: 915587
this should land as part of mergeday fun
Attachment #803595 - Flags: review?(rail)
fixed a typo
Attachment #803595 - Attachment is obsolete: true
Attachment #803595 - Flags: review?(rail)
Attachment #803601 - Flags: review?(rail)
this needs to land on mozilla-aurora after the merge happens
Attachment #803602 - Flags: review?(rail)
we should land this before the merge, we don't build for these targets any more
Attachment #803603 - Flags: review?(rail)
Depends on: 915596
Attachment #803601 - Flags: review?(rail) → review+
Attachment #803602 - Flags: review?(rail) → review+
Comment on attachment 803603 [details] [diff] [review]
clean up m-c b2g configs

DIAF!
Attachment #803603 - Flags: review?(rail) → review+
Whiteboard: [b2g] → [b2g][leave open]
Comment on attachment 803601 [details] [diff] [review]
add b2g builds/tests for mozilla-aurora

Review of attachment 803601 [details] [diff] [review]:
-----------------------------------------------------------------

tweak on location of l10n repos in hg

::: mozilla/b2g_config.py
@@ +946,5 @@
> +######## mozilla-aurora
> +# This is a path, relative to HGURL, where the repository is located
> +# HGURL + repo_path should be a valid repository
> +BRANCHES['mozilla-aurora']['repo_path'] = 'releases/mozilla-aurora'
> +BRANCHES['mozilla-aurora']['gaia_l10n_root'] = 'https://hg.mozilla.org/releases/gaia-l10n/v1_2'

repos will actually be under https://hg.mozilla.org/releases/gaia-l10n/v1_2_0/
Comment on attachment 803602 [details] [diff] [review]
bumps for B2G 1.2 on mozilla-aurora

Review of attachment 803602 [details] [diff] [review]:
-----------------------------------------------------------------

All files need tweak as in emulator-jb/

::: b2g/config/emulator-jb/config.json
@@ +17,4 @@
>      "gaia": {
>          "l10n": {
>              "vcs": "hgtool",
> +            "root": "https://hg.mozilla.org/releases/gaia-l10n/v1_2"

locales will be under "https://hg.mozilla.org/releases/gaia-l10n/v1_2_0/"
(In reply to Hal Wine [:hwine] (use needinfo) from comment #14)
> Comment on attachment 803602 [details] [diff] [review]
> bumps for B2G 1.2 on mozilla-aurora
> 
> Review of attachment 803602 [details] [diff] [review]:
> -----------------------------------------------------------------
> 
> All files need tweak as in emulator-jb/
> 
> ::: b2g/config/emulator-jb/config.json
> @@ +17,4 @@
> >      "gaia": {
> >          "l10n": {
> >              "vcs": "hgtool",
> > +            "root": "https://hg.mozilla.org/releases/gaia-l10n/v1_2"
> 
> locales will be under "https://hg.mozilla.org/releases/gaia-l10n/v1_2_0/"

Clarification here, too, they actually ended up being under https://hg.mozilla.org/releases/gaia-l10n/v1_2/
Depends on: 916911
Still at least partially blocked on the uplift of Gecko 26 & B2G 1.2 from m-c->m-a (see bug 916757)
Awaiting fixes for 916220,915869. 

John, I've added your team to an email thread. please comment on how much time we have left for fixes to land.
Flags: needinfo?(joduinn)
(In reply to Preeti Raghunath(:Preeti) from comment #20)
> Awaiting fixes for 916220,915869. 
> 
> John, I've added your team to an email thread. please comment on how much
> time we have left for fixes to land.

Rail already responded on thread - EOD, at this rate, and assuming no more surprise delays from FF25.0b1.
Flags: needinfo?(joduinn)
Comment on attachment 803602 [details] [diff] [review]
bumps for B2G 1.2 on mozilla-aurora

This is a configuration bump.
Attachment #803602 - Flags: approval-mozilla-aurora?
Attachment #803602 - Flags: approval-mozilla-aurora? → approval-mozilla-aurora+
(looks like gonk-misc is still missing a v1.2 branch -- http://git.mozilla.org/?p=b2g/gonk-misc.git;a=summary)
Depends on: 917692
Aurora desktop B2G localizer builds broken, see bug 917692.
(In reply to Michael Vines [:m1] [:evilmachines] from comment #25)
> (looks like gonk-misc is still missing a v1.2 branch --
> http://git.mozilla.org/?p=b2g/gonk-misc.git;a=summary)

We decided to branch other repos after some feedback from devs.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
(In reply to Rail Aliiev [:rail] from comment #27)
> We decided to branch other repos after some feedback from devs.

v1.2 branches are missing for the following projects.  Is this still in the works?

* librecovery
* gonk-misc
* moztt
Flags: needinfo?(rail)
(In reply to Michael Vines [:m1] [:evilmachines] from comment #28)
> (In reply to Rail Aliiev [:rail] from comment #27)
> > We decided to branch other repos after some feedback from devs.
> 
> v1.2 branches are missing for the following projects.  Is this still in the
> works?
> 
> * librecovery
> * gonk-misc
> * moztt

No decision made regarding branching other repos yet.
Flags: needinfo?(rail)
I see, where is this discussion occurring at?  I'd like to participate.  gonk-misc in particular *should* be branched for v1.2. Probably the rest too.
Flags: needinfo?(rail)
Thanks.  It looks like that discussion has fizzled out unfortunately, so has it been moved to a different bug?  If not, what's the plan to branch the projects I list in comment 28 for v1.2?
Flags: needinfo?(akeybl)
The email thread I had open separately with engineering died down, just brought it back to life. I just want to make sure it's not too early to branch those repos.
Reopening for branch discussion.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Whiteboard: [b2g][leave open] → [b2g][need to resolve 1.2 branching]
librecovery/moztt are pretty low traffic, gonk-misc a little higher.  I guess I'm worried that by not branching at the same time as all the other Moz-owned projects for v1.2, we make (1) things more confusing for devs, and as a result (2) a higher risk of landing non-koi+ in v1.2, and finally this (3) makes me have to watch out for #2 and wonder when the v1.2 branch for these projects will finally occur and when it does ensure we update our manifests.
Flags: needinfo?(akeybl)
I think bug 917173 doesn't strictly block, and we're all done here.
Does anyone think otherwise?
Whiteboard: [b2g][need to resolve 1.2 branching] → [b2g]
Sounds like it.
Let me know if there are any outstanding issues to resolve, other than bug 917173 which doesn't strictly block.
Status: REOPENED → RESOLVED
Closed: 7 years ago7 years ago
Resolution: --- → FIXED
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.