Closed Bug 877752 Opened 13 years ago Closed 13 years ago

set up hg repos in support of b2g18-v1.1hd

Categories

(Release Engineering :: General, defect)

x86
All
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: lsblakk, Assigned: hwine)

References

Details

Attachments

(6 files, 3 obsolete files)

This should live alongside the other b2g repos in releases/mozilla-b2g18_v1_1_0_hd and mimic the behaviour/permissions of mozilla-b2g18_v1_1_0 in every way.
Blocks: 877787
See bug 850482 for details
Assignee: nobody → server-ops-devservices
Component: Release Engineering → Server Operations: Developer Services
QA Contact: shyam
Blocks: 877795
This should be created off of releases/mozilla-b2g18 repo since that is our current development branch for v1.1 work - please tag the mozilla-b2g18 branch when this occurs so we have a record of branching for comparing to uplifts.
Assignee: server-ops-devservices → klibby
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
This bug is for the releng side of the repo setup - undoing incorrect component, etc.
Assignee: klibby → nobody
Status: RESOLVED → REOPENED
Component: Server Operations: Developer Services → Release Engineering: Developer Tools
Depends on: 877814
QA Contact: shyam → hwine
Resolution: DUPLICATE → ---
Summary: Create an hg repo for mozilla-b2g18-v1.1hd repo → set up hg repos in support of b2g18-v1.1hd
branched $ git push origin v1.1.0hd B2G_1_1_0_hd_20130530182315 B2G_1_1_0_hd_20130530182315_BASE Total 0 (delta 0), reused 0 (delta 0) To git@github.com:mozilla-b2g/b2g-manifest.git * [new branch] v1.1.0hd -> v1.1.0hd * [new tag] B2G_1_1_0_hd_20130530182315 -> B2G_1_1_0_hd_20130530182315 * [new tag] B2G_1_1_0_hd_20130530182315_BASE -> B2G_1_1_0_hd_20130530182315_BASE $ git push origin v1.1.0hd B2G_1_1_0_hd_20130530182315 B2G_1_1_0_hd_20130530182315_BASE Total 0 (delta 0), reused 0 (delta 0) To git@github.com:mozilla-b2g/gaia.git * [new branch] v1.1.0hd -> v1.1.0hd * [new tag] B2G_1_1_0_hd_20130530182315 -> B2G_1_1_0_hd_20130530182315 * [new tag] B2G_1_1_0_hd_20130530182315_BASE -> B2G_1_1_0_hd_20130530182315_BASE
Depends on: 878190
Other places to check for branch name subset issues (thanks to Callek): 19:08 < Callek> we'll want to touch http://mxr.mozilla.org/build/source/buildbotcustom/common.py#128 as well as http://mxr.mozilla.org/build/source/tools/buildfarm/maintenance/production-branches.json and do something around http://mxr.mozilla.org/build/source/buildapi/buildapi/scripts/selfserve-agent.py#536 to account for our self-serve hack
Added to push_printurl.py, review via irc: http://hg.mozilla.org/hgcustom/hghooks/rev/13d83c5342bb
Attached patch schema update (obsolete) — Splinter Review
Assignee: nobody → hwine
Status: REOPENED → ASSIGNED
Attachment #756891 - Flags: review?(bugspam.Callek)
Attached file staging/production database update (obsolete) —
Attachment #756892 - Flags: review?(bugspam.Callek)
Comment on attachment 756891 [details] [diff] [review] schema update Review of attachment 756891 [details] [diff] [review]: ----------------------------------------------------------------- ::: sql/data.sql @@ +1573,5 @@ > +insert into machines values (NULL,6,0,NULL,"Linux_mozilla-b2g18_v1_1_0_hd",1,unix_timestamp()); > +insert into machines values (NULL,8,0,NULL,"WINNT_5.2_mozilla-b2g18_v1_1_0_hd",1,unix_timestamp()); > +insert into machines values (NULL,19,0,NULL,"WINNT_6.1_mozilla-b2g18_v1_1_0_hd",1,unix_timestamp()); > +insert into machines values (NULL,17,0,NULL,"OS_X_10.6.2_mozilla-b2g18_v1_1_0_hd",1,unix_timestamp()); > +insert into machines values (NULL,18,0,NULL,"Linux_x86-64_mozilla-b2g18_v1_1_0_hd",1,unix_timestamp()); If I'm to believe surrounding lines we need _leak_test as well.
Attachment #756891 - Flags: review?(bugspam.Callek) → review-
Comment on attachment 756892 [details] staging/production database update see potentially needing _leak_test in the previous patches comment
Attachment #756892 - Flags: review?(bugspam.Callek) → review-
Interesting questions - mozilla-b2g18_v1_0_1 does have leak tests, but mozilla-b2g18 does not. Since this is a clone of b2g18, I went with that configuration.
Attached patch schema updateSplinter Review
with leak tests
Attachment #756891 - Attachment is obsolete: true
Attachment #757520 - Flags: review?
with leak tests
Attachment #756892 - Attachment is obsolete: true
Attachment #757522 - Flags: review?
Attachment #757520 - Flags: review? → review+
Attachment #757522 - Flags: review? → review+
Depends on: 878944
Attachment #758353 - Flags: review?(bhearsum)
Not sure how this will play when there is also mozilla-b2g18_v1_1_0 branch - it may become non-deterministic which abbreviation is used. Anything that we should do now?
Attachment #758354 - Flags: review?(bhearsum)
Attachment #758357 - Flags: review?(bhearsum)
(In reply to Hal Wine [:hwine] from comment #17) > Not sure how this will play when there is also mozilla-b2g18_v1_1_0 branch - > it may become non-deterministic which abbreviation is used. > > Anything that we should do now? AFAIK, the current plan is the B2G 1.1 is the last release that will ship off b2g18, so there shouldn't be another branching off like 1.0.1 did.
Comment on attachment 758354 [details] [diff] [review] path shortening changes for v1.1.0hd support Review of attachment 758354 [details] [diff] [review]: ----------------------------------------------------------------- ::: common.py @@ +126,5 @@ > 'panda': 'p', > 'b2g18': 'b18', > 'v1_0_0': '100', > 'v1_0_1': '101', > + 'v1_1_0_hd': '110hd', Do you need the '_hd' part to make this pass? If not, you can just shorten v1_1_0, which will work for this and the plain v1_1_0 branch, and avoid the race condition.
Comment on attachment 758353 [details] [diff] [review] config changes for v1.1.0hd support Review of attachment 758353 [details] [diff] [review]: ----------------------------------------------------------------- I didn't read this in great detail, but I trust that you copy/pasted well...
Attachment #758353 - Flags: review?(bhearsum) → review+
Attachment #758357 - Flags: review?(bhearsum) → review+
Only shortening v1_1_0 is sufficient - passes test-masters.sh
Attachment #758354 - Attachment is obsolete: true
Attachment #758354 - Flags: review?(bhearsum)
Attachment #758695 - Flags: review?(bhearsum)
Attachment #758695 - Flags: review?(bhearsum) → review+
Attachment #758353 - Flags: checked-in+
Attachment #758695 - Flags: checked-in+
Attachment #758357 - Flags: checked-in+
Live in production.
Status: ASSIGNED → RESOLVED
Closed: 13 years ago13 years ago
Resolution: --- → FIXED
missed gaia branch -> hg repo conversion
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
will be deployed with mapper support enabled
Attachment #759444 - Flags: review?(aki)
Attachment #759444 - Flags: review?(aki) → review+
Comment on attachment 759444 [details] [diff] [review] configs & scheduling for gaia -> hg setup http://hg.mozilla.org/users/hwine_mozilla.com/repo-sync-configs/rev/451a5465eb5c deployed to all production servers
Attachment #759444 - Flags: checked-in+
believe all done here
Status: REOPENED → RESOLVED
Closed: 13 years ago13 years ago
Resolution: --- → FIXED
"Bustage fix" is in production.
Product: mozilla.org → Release Engineering
Component: Tools → General
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: