Build all targets on Android's GN bots

testing/buildbot/chromium.linux.json

Index: testing/buildbot/chromium.linux.json
diff --git a/testing/buildbot/chromium.linux.json b/testing/buildbot/chromium.linux.json
index bfbe0d32ecb9876bab6fc7ca9c203ae38850f938..ff36704ecb331d7e159a02bd64a58499e765931b 100644
--- a/testing/buildbot/chromium.linux.json
+++ b/testing/buildbot/chromium.linux.json
@@ -1,12 +1,7 @@
 {
   "Android GN": {
     "additional_compile_targets": [
-      "chrome_public_apk",
-      "chrome_public_test_apk",
-      "chrome_shell_apk",
-      "chrome_shell_test_apk",
-      "content_shell_apk",
-      "mandoline:all"
+      "all"

[Dirk Pranke, 2015/07/09 15:45:17]

When we ran w/ "all" before, we had problems (at least on debug, I think) that
this ended up being 100GB+ per build. 

Can you confirm that this is no longer the case?

Also, we don't actually build 'all' on any other GN trybot, only on the linux
clobber bot on the main waterfall; instead, we build just the set of test
targets we'd like to be running. Perhaps it makes sense to do the same thing
here?

     ],
     "gtest_tests": [
       {
@@ -64,13 +59,7 @@
   },
   "Android GN (dbg)": {
     "additional_compile_targets": [
-      "chrome_public_apk",
-      "chrome_public_test_apk",
-      "chrome_shell_apk",
-      "chrome_shell_test_apk",
-      "content_shell_apk",
-      "content_shell_test_apk",
-      "mandoline:all"
+      "all"
     ]
   },
   "Android Tests": {