This week the following migrations will be happening:
* 32-bit Linux B2G Desktop builds & tests will be shut off across all
branches.
* 64-bit Linux B2G Desktop builds & tests will migrate to Task Cluster on
trunk branches. We'll circle back and look at release branches later.
* The hg based gaia
Yesterday we stopped running JB/KK/L emulator builds in Buildbot on trunk
branches; these are now all running via Task Cluster.
ICS builds will be migrated over once the tests are greened up.
Cheers!
Chris
___
dev-b2g mailing list
dev-b2g@lists.mozilla.
I'm happy to say that we're beginning to migrate some production workloads
from Buildbot to Task Cluster. The first type of jobs to be migrated over
are the 64-bit Linux mulet builds & tests. These have been running in Task
Cluster for a while now, and we're now disabling them in Buildbot.
https:/
Note that update.boot2gecko.org is going away soon; no active branches of
development are using it.
The current update URL should look like this:
https://aus4.mozilla.org/update/3/%PRODUCT%/%VERSION%/%BUILD_ID%/%PRODUCT_DEVICE%/%LOCALE%/%CHANNEL%/%OS_VERSION%/%DISTRIBUTION%/%DISTRIBUTION_VERSION%/
On 13:22, Tue, 05 Aug, Ed Morley wrote:
The repo mozilla-b2g/B2G is currently not handled by the B2G bumper
bot (script that uses a set of templates in the b2g-manifest repo to
update the manifests in the gecko repo) - and so:
a) It becomes hard for people to land backwards incompatible changes
On 22:58, Mon, 14 Apr, Fabrice Desré wrote:
Hi all,
The situation with updates on b2g is far from being ideal. On one side,
phone manufacturers have little incentive to ship updates for a long
time. On the other side, users legitimately expect to be able to get the
latest version of the OS for a
Hi all,
Just a quick note to say that nightly Tarako builds are now building &
flashing properly.
Get 'em while they're hot
https://pvtbuilds.mozilla.org/pvt/mozilla.org/b2gotoro/nightly/mozilla-b2g28_v1_3t-tarako/latest/
https://pvtbuilds.mozilla.org/pvt/mozilla.org/b2gotoro/nightly/mozilla-
B2G build process? I’m just
wondering if I need to update any of the Build instructions on MDN.
Chris Mills
Senior tech writer || Mozilla
developer.mozilla.org || MDN
cmi...@mozilla.com || @chrisdavidmills
On 17 Jan 2014, at 07:58, Chris AtLee wrote:
Hi,
Yesterday we switched how B2G device
On 13:04, Fri, 17 Jan, Jed Davis wrote:
On Fri, Jan 17, 2014 at 10:58:52AM -0500, Chris AtLee wrote:
Yesterday we switched how B2G device builds on the trunk trees [1]
get built.
We are keeping copies of each device's manifest up-to-date in the
tree will the revisions for each project
Desktop builds continue to use gaia.json. We've added some checks to try
and ensure that the git revision of gaia in the device manifests is the
equivalent of the hg revision of gaia in gaia.json for the desktop
builds.
Desktop builds using gaia.git is blocked on getting git installed
on our
Hi,
Yesterday we switched how B2G device builds on the trunk trees [1] get
built.
We are keeping copies of each device's manifest up-to-date in the tree
will the revisions for each project fully specified. e.g.
https://hg.mozilla.org/integration/b2g-inbound/file/fa8e7793c44b/b2g/config/mako/
I've submitted a pull request on github to correct these two issues:
https://github.com/mozilla-b2g/b2g-manifest/pull/91
Who can review/merge this for me?
Thanks!
Chris
On 09:43, Tue, 13 Aug, Chris AtLee wrote:
Hi B2Gers,
I'm working on enabling JB emulator builds on RelEng'
Hi B2Gers,
I'm working on enabling JB emulator builds on RelEng's automation [1], and
have hit a few snags. I'm hoping the changes to the manifests and/or
repo mirroring will be simple!
tl;dr - I want to switch which repository is used for "gecko" in
base-jb.xml, and change the default remot
On 11:50, Fri, 07 Jun, Tim Chien wrote:
I suggest the Apps team should aware of this and potentially invest
some resource into the Windows build, if we want to fully support FxOS
Simulator as a product.
It's my understanding that the FxOS Simulator doesn't directly depend on
these builds. Can
Windows desktop b2g builds have been pretty broken for several weeks
now, since around May 24 [1].
At this week's engineering and b2g meetings we discussed shutting these
off if nobody has a strong reason to keep them around.
If you are currently depending on the builds for anything, please l
Hi,
Last night we (finally!) made the switch from our snapshot-based builds
to pulling repositories from git using the b2g manifests. This is
effective for mozilla-central and any branches that merge in changes
from m-c.
One restriction we have in place at the moment is that all repositories
It took me a while to understand what you meant about "last green test
run's Gaia master branch commit id". That presumes we're running tests
on gaia master somewhere...where should that be? And with what version
of gecko?
If we can determine a "good" version of gaia, then sure, we can modify
17 matches
Mail list logo
