swarming: add support for cipd on the server side

appengine/swarming/swarming_rpcs.py

Index: appengine/swarming/swarming_rpcs.py
diff --git a/appengine/swarming/swarming_rpcs.py b/appengine/swarming/swarming_rpcs.py
index 0b75e83d9c4c6f306c6dad89557cff62fd6aef25..64671ab6621ffbac699e93480319acb73dcc45af 100644
--- a/appengine/swarming/swarming_rpcs.py
+++ b/appengine/swarming/swarming_rpcs.py
@@ -82,6 +82,14 @@ class FilesRef(messages.Message):
   namespace = messages.StringField(3)
 
 
+class CipdPackage(messages.Message):
+  """A CIPD package to install in $CIPD_PATH and $PATH before task execution."""

[Paweł Hajdan Jr., 2016/04/26 08:45:22]

Quick check: if I'll want to use this to make kitchen use logdog, will I be able
to reference $CIPD_PATH in the swarming command to execute?

We'd request CIPD packages for kitchen and logdog binaries, and I can imagine
the command would look like this:

$CIPD_PATH/kitchen/kitchen ... -logdog-butler-path
$CIPD_PATH/logdog_butler/butler

Does that make sense? I'm also fine with some alternatives, just wanted to make
sure the logdog scenario would work.

This doesn't block the CL of course.

[nodir, 2016/04/29 22:28:08]

Normally CIPD packages have binaries right in the root, which means that both
kitchen and butler binaries will be present in $PATH, so no need to explicitly
reference $CIPD_PATH

+  # Full CIPD package name, e.g. "infra/tools/authutil/linux-amd64"
+  package_name = messages.StringField(1)
+  # Instance ID, tag or ref, e.g. "latest".
+  version = messages.StringField(2)
+
+
 class TaskProperties(messages.Message):
   """Important metadata about a particular task."""
   command = messages.StringField(1, repeated=True)
@@ -93,6 +101,7 @@ class TaskProperties(messages.Message):
   idempotent = messages.BooleanField(7)
   inputs_ref = messages.MessageField(FilesRef, 8)
   io_timeout_secs = messages.IntegerField(9)
+  packages = messages.MessageField(CipdPackage, 10, repeated=True)
 
 
 class NewTaskRequest(messages.Message):