To clarify the repo situation a bit:
- git.mozilla.org/releases/gecko.git only has the released branches for
use by our partners (no other branches), but with CVS history
- github.com/mozilla/mozilla-central has many more branches, and will
be replaced in the near future with one where the sha'
s is confusing for git users.
> It seems to me that the clear winner is the approach in
> github/mozilla/mozilla-central, where all branches are in the one
> repository.
>
> On Tue, Nov 27, 2012 at 5:09 PM, Hal Wine wrote:
>> To clarify the repo situation a bit:
>>
&
mozilla-beta as well (use approval-mozilla-beta?)
>> * Changes that aren't b-b+ must go through
>> approval-mozilla-aurora/approval-mozilla-b2g18 triage
>> * If you have any questions about moving your local builds from mozilla-beta
>> to mozilla-b2g18, please contact H
[dev-b2g to bcc]
On 2013-02-09 17:33 , Justin Lebar wrote:
> Hi, everyone.
>
> I'd like to ask the group if anyone has an objection to naming our b2g
> branches something like "b2g-vX_Y_Z" in gecko.git [1]. I think the
> simplest thing to do is probably to copy the name from the hg
> repository, b
John,
Can you please add QA's recommendation on whether a build should be
promoted to beta? And, if so, which build?
Thanks!
--Hal
On 2013-02-21 17:45 , John Hammink wrote:
> Hi Everyone,
>
>
> 37 out of 46 tests passed for the 2/21/2013 build. Here are the major issues
> that prevented the sm
Marcia,
Usually, we promote the "updated from" build, which is from 3/5. Your
text cites 3/6. Could you please clarify which buildID is to be promoted
to dogfooders? (Dogfooders are currently being offered the 3/4 build.)
Thanks!
--Hal
On 2013-03-08 07:32 , Marcia Knous wrote:
> 3/6 Build OK for
tl;dr: b2g-inbound will replace birch as the place to land b2g work as
of Aug 1, 1000 PT. This has been previously announced in various meetings.
Actions Needed by developers:
- stop using birch prior to Aug 1, 0600 PT (it will be closed then)
- update any birch repositories you have to point to
All trees closed Saturday, Oct 12, from 12:00-16:30 PDT
Original Message
Subject:[Planned Maintenance Notification] - Tree Closure, 2013-10-12
@ 1200 PDT
Date: Thu, 10 Oct 2013 13:51:48 -0700
From: Mozilla IT Operations
To: every...@mozilla.org
Short Summary
Original Message
Subject:[Planned Maintenance Notification] Tree Closure and MTV1
Office Downtime
Date: Fri, 22 Nov 2013 19:34:55 -
From: notificati...@mozilla.com
Short Summary :
Due to a planned power outage in the building that hosts the Mountai
Short Summary :
This is our once in every six weeks planned maintenance window, where IT and
Release Engineering perform maintenance work on critical parts of Mozilla
Infrastructure.
As part of this window, we will begin the move of the tegra infrastructure from
Mountain View to the Santa Clar
As usual, previous try pushes will be discarded. After the reset, try
push times should be improved.
Two improvements since last try reset:
- tbpl has been enhanced to maintain the links to your recent try
pushes that will be lost
- going forward, this will be a standard part of the once per cyc
This work is to further protect against a major cause of tree closures
over the last several weeks.
Original Message
Subject:[Planned Maintenance Notification] fw1.releng.scl3
hardware/software upgrade
Date: Fri, 31 Jan 2014 22:50:38 -
From: net...@mozilla.com
To
Please see below for tree closing activities on Sat, Feb 22 -- including
a reset of the try repo.
Original Message
Subject:[Planned Maintenance Notification] Tree Closure
Date: Wed, 19 Feb 2014 23:20:05 -
From: notificati...@mozilla.com
To: infra-...@mozilla.
FYI: (bcc: release@, sheriffs@)
Original Message
Subject:[Planned Maintenance Notification] 4/5 Tree Closing
Maintenance Window
Date: Tue, 01 Apr 2014 20:32:56 -
Short Summary:
Mozilla IT will have a tree closing maintenance window on Saturday, 4/5, from
0700
With QA's approval, we've spread out the midnight PT start of the
nightly builds on several branches. See https://bugzil.la/998035 for the
details.
Please comment in the bug if this is causing any issues for you.
Thanks!
--Hal (Release Engineering)
___
As some of you are aware, we've been having some capacity issues with
git.mozilla.org of late, which has impacted build times and caused tree
closures.
While we work on longer term fixes, we're going to take the server down
to add addition RAM at 1000PT today.
This will require closing all trees
This work has been completed, and we're back on line with maxed out RAM
for the box!
Special thanks to fubar in dev services and van in dcops for making this
happen so quickly! Go TEAM!
--Hal
On 2014-04-23 08:46 , Hal Wine wrote:
> As some of you are aware, we've been having some ca
Original Message
Subject:[Planned Maintenance Notification] Tree closing maintenance
window
Date: Thu, 15 May 2014 21:28:41 -
From: notificati...@mozilla.com
To: every...@mozilla.org
Short Summary:
Mozilla IT will have a tree closing maintenance window o
All,
Some upstream repositories changed in non-fast-forward manner, and the
automation does not push those changes to our mirrors (as designed).
Per the discussion in bug 1017623 we manually took changes to these 4
repositories. Depending where and how you clone, you may see error
messages from
FYI - some significant network work will be performed during our regular
"Tree Closing Window" (TCW) Saturday, Aug 9, 0900-1200 PT (details below)
We are going to not formally close the trees, but there will likely be
delays (from auto retry) and some jobs might need to be manually
retriggered.
P
tl;dr: try repo is being reset - read on for ways to access old push data
Today we experienced another hg.m.o event that is not recovering similar
to past events. After 2-1/2 hours with no signs of recovery, and with
the recommendation of the sheriffs, we are resetting the try repo now.
While you
See below for details - to check status, please visit #moc in IRC or
https://status.mozilla.org/en-US/calendar/
Main bug for whistlepig: 1065514
Short Summary:
Mozilla IT will have a infrastructure maintenance window on Saturday, September
20th, from 0900-1300 PDT. During this window we will
tl;dr: trees and
buildfarm will be bumpy this Saturday, November 15, from
0300-1400 PT (1100-2200 UTC)
devs will need to monitor their builds, and trigger rebuilds via
self serve as needed.
There may be several short time frames when
tracker bug with details: https://bugzil.la/702
status at: https://treestatus.mozilla.org/
NOTE: the trees will be left open; devs must monitor their own builds,
and retrigger as needed.
IT will be performing maintenance work this Saturday, primarily in SCL3.
That will cause intermittent
tracker bug with details: https://bugzil.la/1123733
status at: https://treestatus.mozilla.org/
NOTE: the trees will be left open; devs must monitor their own builds,
and retrigger as needed.
IT will be performing maintenance work this Saturday, primarily in SCL3.
That will cause intermittent
FYI, recent commits to gecko on hg.mozilla.org will be delayed in
arriving at github.com:mozilla/gecko-dev.git This likely includes
anything landed after approximate 2000PT Wednesday.
Forwarded Message
Subject: gecko-dev and Git replication will be broken for a little while
D
details in https://bugzil.la/927219#c45
On 2015-01-29 07:12 , Hal Wine wrote:
FYI, recent commits to gecko on hg.mozilla.org will be delayed in
arriving at github.com:mozilla/gecko-dev.git This likely includes
anything landed after approximate 2000PT Wednesday.
Forwarded
All work was completed on Monday and services fully restored. If you are
experiencing any issues, please contact #vcs.
NOTE: if you use the remote git.mozilla.org/integration/gecko-dev.git
please keep reading.
If you use this particular remote, and pulled during the problem window
(roughly J
tl;dr: if you reference git://gitmirror.mozilla.org/mozilla-b2g/gaia,
please change to git://git.mozilla.org/releases/gaia.git
gitmirror.mozilla.org gets overloaded from time to time. To reduce load,
we will be removing dead repositories and repositories already mirrored
to git.mozilla.org. (s
tracker bug with details: https://bugzil.la/1141402
status at: https://treestatus.mozilla.org/
IT and Release Operations will be performing maintenance work this
Saturday. The work is expected to be invasive, and we will close the
trees for the duration of the window, 8 hours from 0600 PDT to 1
tracker bug with details: https://bugzil.la/1151645
status at: https://treestatus.mozilla.org/ for trees
status at: https://whistlepig.mozilla.org/en-US/detail/302/ for event
IT will be performing maintenance work this Saturday. The work is
expected to be invasive, and we will close the trees fo
Trees will be closed, and other services (such as bugzilla) unavailable
for periods of time.
Forwarded Message
Subject: [Planned] Tree Closing Maintenance Window, Sat May 23 2015,
0800-1800 PT
Date: Wed, 20 May 2015 19:19:11 -
From: m...@mozilla.com
To:
Issu
tracker bug with details: https://bugzil.la/1175630
status at: https://whistlepig.mozilla.org/en-US/detail/368/
NOTE: the trees will be left open; devs must monitor their own builds,
and retrigger as needed.
IT will be performing maintenance work this Saturday, primarily in SCL3.
That will ca
If you want to follow along, the tracking bug is https://bugzil.la/1182561
-- Forwarded message --
From:
Date: Mon, Jul 13, 2015 at 10:32 AM
Subject: [Planned ] Scheduled Tree Closing and disruptive IT Maintenance
Window, Sat July 18 2015, 0700-1400 PT
To: all-moco-m...@mozilla.co
FYI - all trees closed, and hg.mozilla.org will be unavailable for commits
as well.
Tracking bug is https://bugzil.la/1197981 if you want to follow along
-- Forwarded message --
From:
Date: Tue, Aug 25, 2015 at 8:46 AM
Subject: [Planned] Scheduled Tree Closing and IT Maintenance W
35 matches
Mail list logo
