Even though most of the time friendly names like "XPCShell" are better to see than the buildbot job name, there are times when it is necessary to know what buildbot calls a job, whether it's to talk to releng or to filter in releng tools. Not having any way to see the full jobname also makes it difficult to diagnose wtf when treeherder doesn't properly recognize something: right now, both "b2g_ubuntu64_vm mozilla-inbound opt test gaia-unit" and "b2g_ubuntu64_vm mozilla-inbound opt test gaia-unit-oop" are shown as "Gaia Unit Test" and you have to have external knowledge to know why there are two, one broken, while "b2g_ubuntu64_vm mozilla-inbound opt test mochitest-oop-1" is shown as a "?" "Mochitest" requiring even more external knowledge to guess wtf it is.
Yeah agree with this. Perhaps we should add another entry to the job metadata list, called "Buildbot job name" - I guess we could tuck it away under a "show more" list?
https://github.com/mozilla/treeherder-ui/commit/2ffba5c97ea8f6e94ba36e86d9317c628700639d and https://github.com/mozilla/treeherder-ui/commit/4c7d724ff20834a6456ad9c062c76fbb7edcb20f If it's a buildbot job, then it'll show, otherwise not.
Commits pushed to master at https://github.com/mozilla/treeherder https://github.com/mozilla/treeherder/commit/b7fcdd3cb90d9d66e0293889ab6518312a07bee8 fix bug 1031858: add buildername to the detail panel https://github.com/mozilla/treeherder/commit/e3c5196e0ab6e00b9f7bf23c08cd92c7d4f3edd0 Fix bug 1031858 #2: updated the field name to match suggestion in bug