Nice. It would be great to get some more of this stuff on MDN at some point, but for now, I’ve just added links to our Firefox OS TBPL page:
https://developer.mozilla.org/en-US/Firefox_OS/TBPL Could someone have a quick read through this and let me know if it makes sense? It’s only short. many thanks, Chris Mills Senior tech writer || Mozilla developer.mozilla.org || MDN [email protected] || @chrisdavidmills On 14 Feb 2014, at 00:53, Jonathan Griffin <[email protected]> wrote: > We know that Gaia developers have long wanted the ability to use custom Gaia > builds in TBPL try jobs, mostly to help debug TBPL-specific failures in Gaia > tests. This has been a challenge, given the tight coupling of much of the > related tooling with hg. > > We now have a partial solution to this; it does require using hg, but still > allows you to use your own Gaia forks in github for the try jobs. The method > is described here: > https://wiki.mozilla.org/ReleaseEngineering/TryServer#Using_a_custom_Gaia > > If you've never pushed to try, you'll want to read the basic instructions > here: https://wiki.mozilla.org/ReleaseEngineering/TryServer#How_to_push_to_try > > Like all try jobs, this requires Level 1 commit access (see > http://www.mozilla.org/hacking/commit-access-policy/). If you want to run > all tests on B2G Desktop builds with your custom Gaia fork, the correct > trychooser syntax is: "try: -b o -p > linux64_gecko,linux32_gecko,macosx64_gecko -u all -t none". > > Jonathan > > _______________________________________________ > dev-b2g mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-b2g _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
