Bugzilla

So the different values of run-on-projects that we have for tier 1 jobs at the moment are:
- all
- release
- release, integration, try
- mozilla-beta
- mozilla-beta, trunk, try
- mozilla-beta, autoland, try
- mozilla-central
- mozilla-central, trunk, try
- mozilla-central, try
- mozilla-central, integration
- trunk, try
- try

First, I'll note that "mozilla-central, integration" is the mostly same as "trunk" (trunk includes comm-central, but I don't think this matters, comm-central uses different yaml definitions auiu)

Similarly, "mozilla-central, trunk, try" is the same as "trunk, try".

The "mozilla-beta, autoland, try" one is weird. Why autoland specifically, and not integration?
  - */
"release, integration, try" is kind of confusing. "release, trunk, try" would be the same thing, but less confusing.

Now, looking at all the tier 1 jobs that aren't balrog, beetmover, build-signing, cron-bouncer-check, checksums-signing, docker-image, fetch, mar-signing, nightly, packages, pipfile-update, release-*, repackage, repo-update, toolchain, upload-generated-sources or devedition, we're left with:
- A bunch of tests set run_on_projects for an explicit disable on some platforms. I'd say ideally we shouldn't even create tasks for those.
- */opt-browser-screenshots-e10s run on trunk but not try.
- The following tasks run on mozilla-central only (not integration, not try):
  - addon-tps-xpi
  - build-android-api-16-ccov/debug
  - build-android-api-16-without-google-play-services/opt
  - build-android-test-ccov/opt
  - all serviceworker-e10s tests
- The following tasks run on mozilla-central or try, but not integration:
  - build-linux64-asan-fuzzing-ccov/opt
  - build-linux64-fuzzing-ccov/opt
  - build-macosx64-ccov/debug
  - test-android-hw-p2-8-0-android-aarch64/opt-raptor-speedometer-geckoview-power-e10s
  - test-android-hw-p2-8-0-arm7-api-16/opt-raptor-speedometer-geckoview-power-e10s
  - test-linux64-pgo/opt-talos-sessionrestore-many-windows-e10s
  - test-linux64-qr/opt-talos-sessionrestore-many-windows-e10s
  - test-linux64/opt-talos-sessionrestore-many-windows-e10s
  - test-macosx64/opt-talos-sessionrestore-many-windows-e10s
  - test-windows10-64-pgo/opt-talos-sessionrestore-many-windows-e10s
  - test-windows10-64-qr/opt-talos-sessionrestore-many-windows-e10s
  - test-windows10-64/opt-talos-sessionrestore-many-windows-e10s
  - test-windows7-32-pgo/opt-talos-sessionrestore-many-windows-e10s
  - test-windows7-32/opt-talos-sessionrestore-many-windows-e10s
- The following tasks don't run on mozilla-central (in fact, they only run on try):
  - */opt-awsy-base-dmd-e10s
  - */opt-awsy-dmd-e10s
  - */*-upload-symbols

So the different values of run-on-projects that we have for tier 1 jobs at the moment are:
- all
- release
- release, integration, try
- mozilla-beta
- mozilla-beta, trunk, try
- mozilla-beta, autoland, try
- mozilla-central
- mozilla-central, trunk, try
- mozilla-central, try
- mozilla-central, integration
- trunk, try
- try

First, I'll note that "mozilla-central, integration" is the mostly same as "trunk" (trunk includes comm-central, but I don't think this matters, comm-central uses different yaml definitions auiu)

Similarly, "mozilla-central, trunk, try" is the same as "trunk, try".

The "mozilla-beta, autoland, try" one is weird. Why autoland specifically, and not integration?

"release, integration, try" is kind of confusing. "release, trunk, try" would be the same thing, but less confusing.

Now, looking at all the tier 1 jobs that aren't balrog, beetmover, build-signing, cron-bouncer-check, checksums-signing, docker-image, fetch, mar-signing, nightly, packages, pipfile-update, release-*, repackage, repo-update, toolchain, upload-generated-sources or devedition, we're left with:
- A bunch of tests set run_on_projects for an explicit disable on some platforms. I'd say ideally we shouldn't even create tasks for those.
- \*/opt-browser-screenshots-e10s run on trunk but not try.
- The following tasks run on mozilla-central only (not integration, not try):
  - addon-tps-xpi
  - build-android-api-16-ccov/debug
  - build-android-api-16-without-google-play-services/opt
  - build-android-test-ccov/opt
  - all serviceworker-e10s tests
- The following tasks run on mozilla-central or try, but not integration:
  - build-linux64-asan-fuzzing-ccov/opt
  - build-linux64-fuzzing-ccov/opt
  - build-macosx64-ccov/debug
  - test-android-hw-p2-8-0-android-aarch64/opt-raptor-speedometer-geckoview-power-e10s
  - test-android-hw-p2-8-0-arm7-api-16/opt-raptor-speedometer-geckoview-power-e10s
  - test-linux64-pgo/opt-talos-sessionrestore-many-windows-e10s
  - test-linux64-qr/opt-talos-sessionrestore-many-windows-e10s
  - test-linux64/opt-talos-sessionrestore-many-windows-e10s
  - test-macosx64/opt-talos-sessionrestore-many-windows-e10s
  - test-windows10-64-pgo/opt-talos-sessionrestore-many-windows-e10s
  - test-windows10-64-qr/opt-talos-sessionrestore-many-windows-e10s
  - test-windows10-64/opt-talos-sessionrestore-many-windows-e10s
  - test-windows7-32-pgo/opt-talos-sessionrestore-many-windows-e10s
  - test-windows7-32/opt-talos-sessionrestore-many-windows-e10s
- The following tasks don't run on mozilla-central (in fact, they only run on try):
  - \*/opt-awsy-base-dmd-e10s
  - \*/opt-awsy-dmd-e10s
  - \*/\*-upload-symbols