Adding Variable builders to cover all builders under master "chromium"

masters/master.tryserver.chromium.android/builders.pyl

Index: masters/master.tryserver.chromium.android/builders.pyl
diff --git a/masters/master.tryserver.chromium.android/builders.pyl b/masters/master.tryserver.chromium.android/builders.pyl
index 42f588e1c75a9d82a229ba5081ae5efd10d89e83..d5ea3b327e8de10ad47aaea8bf026b6cc663b325 100644
--- a/masters/master.tryserver.chromium.android/builders.pyl
+++ b/masters/master.tryserver.chromium.android/builders.pyl
@@ -142,7 +142,14 @@
       "scheduler": None,
       "slavebuilddir": "android_chromium_variable",
       "slave_pools": ["ccompute_bots_cq"],
-    }
+    },
+    "android_chromium_variable_archive": {
+      "builder_timeout_s": 6900,  # 60 * 115
+      "recipe": "findit/chromium/compile",
+      "scheduler": None,
+      "slavebuilddir": "android_chromium_variable_archive",
+      "slave_pools": ["ccompute_bots_cq"],

[Sergey Berezin, 2016/03/16 01:52:20]

The disk space on this pool is very healthy, adding a new build folder is fine:
http://shortn/_qIec7MCxuZ

However, please keep in mind that this pool is already slightly overloaded:
https://goto.google.com/salqx

[stgao, 2016/03/16 07:32:58]

Jeff, we need to be careful about using cq slave pools.
Is it possible to have an optional slave pool like those in win/mac/linux
tryservers that we use?

+    },
   },
 
   "schedulers": { },