This work is pending being able to do a swarming build on a specified pool.

Status: I will wait for @don to give me a testable builder, then start.

Pass to CI team.

Pri-0 bugs are critical regressions or serious emergencies, and this bug has not been updated in three days. Could you please provide an update, or adjust the priority to a more appropriate level if applicable?

If a fix is in active development, please set the status to Started.

Thanks for your time! To disable nags, add the Disable-Nags label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

At a first glance, to remove the whitelisting will require us to utilize service accounts for connecting.  Based on our current implementation, service accounts will require the deployment and configuration of the cloud proxy to all builders.  

Separate bugs will be opened to track those initiatives.  

-- Mike

My understanding is that we have to deploy the proxy, and manage it's runtime process ourselves (not as a system service). That is feasible, but a little more tricky, probably similar to what we do with tsmon today.

Why could this not be deployed/started as a service?  Normally all dependent services that are not part of the actual build process, would be started and managed as a service.  

Is there something specific here that would prevent that?  

-- Mike

Maybe it can, I'm not sure.