The amd64-generic Trusty (Informational) builder:
https://uberchromegw.corp.google.com/i/chromeos.chrome/builders/amd64-generic%20Trusty%20%28Informational%29

Is configured in the chrome internal build tools:
https://chrome-internal.googlesource.com/chrome/tools/build_limited/scripts/slave.git/+/master/recipes/chrome.expected/full_chromeos_chrome_amd64_generic_Trusty__Informational_.json

However, the builder lives on a chromeos waterfall. See  issue 633350 #c7 for more details.

This builder (which recently broke during the GN migration) tests Simple Chrome ('cros chrome-sdk') with --internal.

We have similar builders on the chromium waterfall that test 'cros chrome-sdk' but without --internal. These are configured in the chromium repo under tools/mb.

ChromiumOS [amd64-generic|x86-generic|daisy] Compile:
https://build.chromium.org/p/chromium.chromiumos/builders/ChromiumOS%20amd64-generic%20Compile
https://build.chromium.org/p/chromium.chromiumos/builders/ChromiumOS%20daisy%20Compile
https://build.chromium.org/p/chromium.chromiumos/builders/ChromiumOS%20x86-generic%20Compile

All four of these are important for maintaining Simple Chrome. However we should:
a) Name them consistently and clearly.
b) Configure them in a way that is maintainable by a cros infra/product support team.