Closed
Bug 813421
Opened 12 years ago
Closed 12 years ago
mirror git.m.o:releases/gaia to hg
Categories
(Release Engineering :: General, defect)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: hwine, Assigned: hwine)
References
Details
(Whiteboard: [re-b2g])
We need to repo being updated in hg to trigger the build on commit support.
Comment 1•12 years ago
|
||
Do you know how the git branches relation will be?
I see three gaia repos:
* gaia
* gaia-central
* gaia-nightly
Thanks a lot!
Assignee | ||
Comment 2•12 years ago
|
||
(In reply to Armen Zambrano G. [:armenzg] from comment #1)
> Do you know how the git branches relation will be?
Below is the plan as it stands now.
> I see three gaia repos:
We are pursuing 2 strategies in parallel, as we're not positive about the first one. Once a strategy is picked, the repos supporting the other strategy will be deleted.
> * gaia
"Gaia" supports the preferred strategy, where the git RoR is converted to a single hg repo using hg bookmarks to track the git branches.
This approach will allow other branches to be added seemlessly to the RoR (e.g. we expect a "stable" at some point).
> * gaia-central
> * gaia-nightly
'gaia-central' and 'gaia-nightly' support the backup strategy where each git branch is mirrored to a separate hg repo. 'gaia-central' will track the 'master' (default trunk) branch. 'gaia-nightly' will track the 'nightly' branch.
Addition of other branches will require standing up additional repos and conversion tooling.
Updated•12 years ago
|
Blocks: b2g-testing-track
Comment 3•12 years ago
|
||
So, we have https://hg.mozilla.org/integration/gaia now....but it has almost 4,000 heads. This means we get these errors when cloning:
➜ b hg clone https://hg.mozilla.org/integration/gaia/
destination directory: gaia
requesting all changes
abort: HTTP Error 413: Request Entity Too Large
Which means it's not very useful to us =\. We don't have the ability to clone over ssh from slaves.
Assignee | ||
Comment 4•12 years ago
|
||
Status Update:
- single branch per repo now available:
http://hg.mozilla.org/integration/gaia-nightly <= git nightly branch
http://hg.mozilla.org/integration/gaia-central <= git master branch
- still working on reducing # heads in the preferred format repo:
http://hg.mozilla.org/integration/gaia <= all git branches as bookmarks
Comment 5•12 years ago
|
||
https://hg.mozilla.org/integration/gaia-nightly appears to broken now. I'm getting ISE 500 from it, and hgweb doesn't look good.
Assignee | ||
Comment 6•12 years ago
|
||
(In reply to Ben Hearsum [:bhearsum] from comment #5)
> https://hg.mozilla.org/integration/gaia-nightly appears to broken now. I'm
> getting ISE 500 from it, and hgweb doesn't look good.
working now - I believe this was likely caused by a hung hg push to that repo from the conversion box. The hang was caused by the initial push (large) being rejected by hg for failing to pass the commit-message.py hook. bug 815967 resolved that issue this morning, and no problems have been observed since.
Assignee | ||
Comment 7•12 years ago
|
||
(In reply to Hal Wine [:hwine] from comment #4)
> Status Update:
> - single branch per repo now available:
> http://hg.mozilla.org/integration/gaia-nightly <= git nightly branch
> http://hg.mozilla.org/integration/gaia-central <= git master branch
There were some update issues after this, due to configuration on the hg
server. Resolved via bug 815967
- preferred (bookmarked) format available - only one head per
bookmark:
http://hg.mozilla.org/integration/gaia <= all git branches as bookmarks
That completes this work. Please report issues as new bugs.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
Updated•8 years ago
|
Component: Tools → General
You need to log in
before you can comment on or make changes to this bug.
Description
•