Donald King

Correct. Per the advice of our Google PSO team, having separate projects is the best way to enforce security boundaries, and we have security boundaries aplenty with our Jenkins setup....

Example: ```sh export http_proxy="http://some.proxy:3128" export https_proxy="http://some.proxy:3128" export no_proxy="localhost,.internal,169.254.169.254" # usual Jenkins start-up java -jar slave.jar # now all subprocesses started on this executor by Jenkins have $http_proxy set ``` There...

It might help to know that we have a mix of executor types: cloud VMs that Jenkins deploys, bare metal machines that Jenkins SSHes into, and Mac Minis that live...

  `cloud.project` is `something-jenkins-prod` `cloud.imageProject` is `something-packer-prod` This works, but if I click "save" then it corrupts the plugin configuration.

We haven't had time to upgrade from 1.0.5 (we're several months behind on our patching for all plugins, not just GCE).

Considering that we're building a new image every day, then garbage collecting the images that aren't tagged as in-use, I'd really like to not have to copy the images to...