Closed
Bug 626874
Opened 14 years ago
Closed 14 years ago
project branch for services: services-central
Categories
(Release Engineering :: General, defect, P3)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: mconnor, Assigned: lsblakk)
References
Details
Attachments
(1 file)
4.14 KB,
patch
|
catlee
:
review+
lsblakk
:
checked-in+
|
Details | Diff | Splinter Review |
> Name of hg repo for this branch (relative to hg.mozilla.com)
services-central will be the repo, it'll live in /services for our own sanity.
Expected home is: https://hg.mozilla.org/services/services-central
> NOTE: this name will be used for all things related to the branch, tinderbox, tbpl, ftp locations, etc.
> Has a bug already been filed to create the repo?
Bug 626859
> Name of parent branch?
This will be based off mozilla-central trunk.
> Do you want builds?
> All o.s. or subset of linux32, linux64, osx10.5, osx10.6, win32, win64
Yes, all of the above
> Incremental-build-on-checkin? y/N
y
> Nightly builds? Y/n
Not initially, possible in future.
> Nightly updates? y/N
Not initially, possible in future.
> Do you want unittests?
> All o.s. or subset of: WinXP, Win7, 10.5, 10.6, fedora12, fedora12-64, maemo4, maemo5gtk, maemo5qt, android (with Win7x64 coming soon).
Yes, all OS.
> Do you need mobile builds?
> All o.s. or subset of linux-i686, macosx-i686, maemo4, maemo5gtk, maemo5qt
Yes. Subset: Android and N900, whatever those correspond to.
> Incremental-build-on-checkin? y/N
Yes.
> Do you want talos?
> Do you need talos on Tiger?
> All o.s. or subset of Talos platforms?
Yes. No Tiger, all other OS.
> Name of the contact person for this branch who will:
> Be doing periodic refreshes from parent
Philipp (philikon@mozilla.com)
> Be contact person for misc setup questions
mconnor (mconnor@mozilla.com)
> Decide when to land back project branch onto parent
mconnor (mconnor@mozilla.com) (but will be ongoing)
> Decide when to terminate the project branch
mconnor (mconnor@mozilla.com)
> Timeline:
> Is this branch is needed for a specific hard calendar deadline? (we typically can do this in 2 weeks, and we will notify you if we think we'll miss that)
Target date is Feb 28th
> For changes in schedule, or status checks, please ping in bug.
> Approx expected life span of project branch - if known?
∞
> Additional requests:
> By default project branches do not have l10n:
> this requires significantly more resources, please be sure its justified
> which l10n repos do you want to use? Or do you want to project branch all l10n repos also?
> needing l10n will make setup of project branch take significantly longer
No l10n.
> Need any changes to toolchain used in parent branch?
No.
> Need any changes to the compile/link/repack steps used in parent branch?
No.
> Do you expect to create any releases from this project branch?
No.
> NOTE: Currently we do not have nightly/alpha/beta/release updates on these project branches.
> Any other info that might be helpful to us?
This is awesome.
Assignee | ||
Comment 1•14 years ago
|
||
see bug 626874 where more branches are being set up for re-usable projects and will be able to read from custom repos if needed (ie: not in hg.m.o/projects/)
Assignee | ||
Comment 2•14 years ago
|
||
(In reply to comment #1)
Wrong bug # - see bug 627454
Depends on: 627454
Assignee | ||
Updated•14 years ago
|
Priority: -- → P3
Assignee | ||
Updated•14 years ago
|
Assignee: nobody → lsblakk
Reporter | ||
Updated•14 years ago
|
Summary: release branch for services: services-central → project branch for services: services-central
Assignee | ||
Comment 3•14 years ago
|
||
Mike can you make an initial commit to the services/services-central repo so that I can test in staging? Without the 'default' branch my tests are failing. Preferable a revision that will make it through compile.
Comment 4•14 years ago
|
||
It would be appreciated if you ask IT to clone mozilla-central to your new repo, rather than push all the history of m-c to an empty one. Buildbot will have a nasty time if the json version of pushlog is OMG massive.
Reporter | ||
Comment 5•14 years ago
|
||
filed bug 634338 to get the cloning done.
Assignee | ||
Comment 6•14 years ago
|
||
Graphserver production is ready, test builders are ready and waiting for builds, Tinderbox page exists, just need builds to be in ACTIVE_BRANCHES
Attachment #513248 -
Flags: review?(catlee)
Updated•14 years ago
|
Attachment #513248 -
Flags: review?(catlee) → review+
Assignee | ||
Comment 7•14 years ago
|
||
Comment on attachment 513248 [details] [diff] [review]
turn on services-central branch in production
landed on default: http://hg.mozilla.org/build/buildbot-configs/rev/e13197192c1d
Attachment #513248 -
Flags: checked-in+
Assignee | ||
Comment 8•14 years ago
|
||
This branch is now live in production and is ready for use. Please push to it twice to kick it off, the first set of builds should go red because there won't be logs to compare to, but the second run of builds should complete properly.
Comment 9•14 years ago
|
||
Pushed the current m-c tip to it. m-c is closed for now so the second push will have to wait a bit.
Filed bug 636047 for getting a tbpl interface for this branch.
Assignee | ||
Comment 10•14 years ago
|
||
Looks like the branch is working as expected, I see everything on the Tinderbox page. Closing.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Updated•12 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•