For the same reasons cited in Bug 862595 we need the build type and job type in dedicated build properties. Downstream consumers use an unreliable complicated mix of properties, regular expressions, conditional logic, and whitelist strategies to determine these values. Examples: [ 'build_type', 'opt|debug|pgo|...' ] [ 'job_type', 'build|unittest|talos|repack|...' ]
A few thoughts here... An "easy" way to get going here is to add some more checks here: http://hg.mozilla.org/build/buildbot-configs/file/03127b8a1025/mozilla/builder_master.cfg#l186 I was also wondering if it's better to use a more generic "job_tags" that can have a list of tags rather than specific build_type, job_type fields. I'm not confident at this point that we can accurately describe all the various types of jobs that are run with two attributes.
Please use a tags field for this. It would make querying data *extremely* easier. Furthermore, you can add new tags as we think of them without altering any database schemas.
Given bug 1031238 comment 2, should this be marked WONTFIX as well?