We should be able to generate it from buildbot-configs. I started messing with it and it should be doable. Do you know of anyone that has attempted this before?

(In reply to Armen Zambrano [:armenzg] (EDT/UTC-4) from comment #0) > We should be able to generate it from buildbot-configs. > I started messing with it and it should be doable. > > Do you know of anyone that has attempted this before? Armen: how far did you get here? Is there any WIP to point people at?

No. I did not managed to put enough time to get a wip.

The information can be extracted from here: http://people.mozilla.org/~catlee/allthethings.json The current code is in here: http://hg.mozilla.org/build/tools/file/default/trychooser The current web view is in here: http://trychooser.pub.build.mozilla.org For instance, we can determine the list of a available build jobs from [1] and [2]. Given one of the builders, e.g. "Android 4.2 x86 try build" we can find the platform that triggers it [3] which is: "platform": "android-x86"," We can then determine which test jobs listen to android-x86 to build the list associated to it. I have in my mind a UI that will make things more beautiful once we have a graph of dependencies generated. [1] "try-firefox": { "downstream": [ "Android 2.2 Armv6 try build", "Android 2.2 Debug try build", "Android 2.2 try build", "Android 4.2 x86 try build", "Linux try build", "Linux try leak test build", "Linux try pgo-build", "Linux x86-64 try asan build", "Linux x86-64 try build", "Linux x86-64 try debug asan build", "Linux x86-64 try debug static analysis build", "Linux x86-64 try leak test build", "Linux x86-64 try pgo-build", "Linux x86-64 try valgrind", "OS X 10.7 64-bit try leak test build", "OS X 10.7 try build", "WINNT 5.2 try build", "WINNT 5.2 try leak test build", "WINNT 5.2 try pgo-build", "WINNT 6.1 x86-64 try build", "WINNT 6.1 x86-64 try leak test build", "linux64-br-haz_try_dep", "linux64-sh-haz_try_dep" ] }, [2] "b2g_try-b2g": { "downstream": [ "b2g_try_emulator-debug_dep", "b2g_try_emulator-jb-debug_dep", "b2g_try_emulator-jb_dep", "b2g_try_emulator-kk-debug_dep", "b2g_try_emulator-kk_dep", "b2g_try_emulator_dep", "b2g_try_linux32_gecko build", "b2g_try_linux64_gecko build", "b2g_try_macosx64_gecko build", "b2g_try_win32_gecko build" ] }, [3] "Android 4.2 x86 try build": { "properties": { "branch": "try", "platform": "android-x86", "product": "firefox", "slavebuilddir": "try-and-x86-000000000000000000", "stage_platform": "android-x86" }, "shortname": "try-android-x86", "slavebuilddir": "try-and-x86-000000000000000000", "slavepool": "acfbcb424e5d81a16691f25875a7d77d949c9198" }, [4] "Android 4.2 x86 Emulator try opt test androidx86-set-4": { "properties": { "branch": "try", "platform": "android-x86", "product": "mobile", "repo_path": "try", "script_repo_revision": "production", "slavebuilddir": "test", "stage_platform": "android-x86" }, "shortname": "try_ubuntu64_hw_test-androidx86-set-4", "slavebuilddir": "test", "slavepool": "131acb84ca1c0b9db74a6df032310401fa91c53a" },

I have filed this: https://github.com/armenzg/mozilla_ci_tools/issues/69 Hopefully someone picks it up.

Some jobs are not enabled by default on try when we choose "all" and have to be specific to trigger them. We need that data in allthethings.json (bug 1110847).

This is the current structure we can generate from mozilla ci tools with this: python scripts/misc/write_tests_per_platform_graph.py