Archive dartium on android builds

tools/bots/bot_utils.py

Index: tools/bots/bot_utils.py
===================================================================
--- tools/bots/bot_utils.py	(revision 33324)
+++ tools/bots/bot_utils.py	(working copy)
@@ -116,11 +116,18 @@
     return '/'.join([self.apidocs_directory(revision),
       self.apidocs_zipfilename()])
 
+  def dartium_android_apk_filepath(self, revision):
+    return '/'.join([self.dartium_android_directory(revision),
+      self.dartium_android_apk_filename()])
+
   # Functions for querying gs:// directories
 
   def dartium_directory(self, revision):
     return self._variant_directory('dartium', revision)
 
+  def dartium_android_directory(self, revision):
+    return self._variant_directory('dartium_android', revision)
+
   def sdk_directory(self, revision):
     return self._variant_directory('sdk', revision)
 
@@ -142,6 +149,9 @@
 
   # Functions for quering filenames
 
+  def dartium_android_apk_filename(self):
+    return 'Chrome.apk'

[kustermann, 2014/03/06 09:20:36]

I'd prefer if we can differentiate between release/debug, arm/arm64. Just do it
like we do for normal dartium, i.e.:

.../dartium/dartium-android-arm-release.apk
.../dartium/content_shell-android-arm-debug.apk

I.e. use the functionality in "dartium_variant_zipfilename"

[ricow1, 2014/03/06 11:49:05]

valid point, I will add that

+
   def apidocs_zipfilename(self):
     return 'dart-api-docs.zip'
 
@@ -249,6 +259,14 @@
     args += [local_path, remote_path]
     self.execute(args)
 
+  def setGroupReadACL(self, remote_path, group):
+    args = ['acl', 'ch', '-g', '%s:R' % group, remote_path]
+    self.execute(args)
+
+  def setContentType(self, remote_path, content_type):
+    args = ['setmeta', '-h', 'Content-Type:%s' % content_type, remote_path]
+    self.execute(args)
+
   def remove(self, remote_path, recursive=False):
     assert remote_path.startswith('gs://')