Aren't CrOS TPMs handling release waterfall configuration?

ok, I posted https://chromium-review.googlesource.com/#/c/332192/ to enable moblab-release 

Builder needs to be allocated after that is merged, right?

Yep, once it lands file a trooper ticket at go/bug-a-trooper for CrOS pin bump + restart for master "chromeos_release" and the release branch that you modified.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/chromite/+/0363ed6345e83ad92c3d4641bd66939946fc3eaa

commit 0363ed6345e83ad92c3d4641bd66939946fc3eaa
Author: Josafat Garcia <josafat@google.com>
Date: Wed Mar 16 01:43:14 2016

Add guado_moblab to M50

BUG= chromium:593857 
TEST=None

Change-Id: I3c8d890f9b8fe0c9495d4a96a36aed5245fb8f10
Reviewed-on: https://chromium-review.googlesource.com/332278
Reviewed-by: Bernie Thompson <bhthompson@chromium.org>
Reviewed-by: Josafat Garcia <josafat@chromium.org>
Commit-Queue: Josafat Garcia <josafat@chromium.org>
Tested-by: Josafat Garcia <josafat@chromium.org>

[modify] https://crrev.com/0363ed6345e83ad92c3d4641bd66939946fc3eaa/cbuildbot/config_dump.json
[modify] https://crrev.com/0363ed6345e83ad92c3d4641bd66939946fc3eaa/cbuildbot/chromeos_config.py

ok, config change landed


Dan, can you pass it to the troopers for next steps as per c#5

Hi Dan, Pinging back to check if you can pass this to troopers per #5

Any reason you can't file the ticket as per the instructions in #5? I don't think I need to be a middleman here.

Thanks. Done https://bugs.chromium.org/p/chromium/issues/detail?id=595918

This request has been completed: https://uberchromegw.corp.google.com/i/chromeos_release/builders/guado_moblab-release%20release-R50-7978.B