Switch Android Builder on chromium.webkit to gn.

tools/mb/mb_config.pyl

Index: tools/mb/mb_config.pyl
diff --git a/tools/mb/mb_config.pyl b/tools/mb/mb_config.pyl
index 23ba935f8aea6510e819dae62bad068e17a9b366..00599b9bbac1fc5f1cb044c51e92913277530d23 100644
--- a/tools/mb/mb_config.pyl
+++ b/tools/mb/mb_config.pyl
@@ -540,8 +540,8 @@
     },
 
     'chromium.webkit': {
-      'Android Builder': 'gyp_release_bot_android',
-      'WebKit Android (Nexus4)': 'gyp_release_bot_android',
+      'Android Builder': 'android_gn_release_bot_minimal_symbols',
+      'WebKit Android (Nexus4)': 'none',

[Dirk Pranke, 2016/04/19 22:12:58]

So you're going to make Android Builder trigger WebKit Android (Nexus4) via some
build-side change?

Hopefully it'll pull in all of the right targets ...

I'd be more inclined to just flip both bots to GN now, and change to triggering
in a separate change.

[jbudorick, 2016/04/19 22:17:51]

I'm confused -- WebKit Android (Nexus4) already appears to be triggered by
Android Builder:
https://chromium.googlesource.com/chromium/tools/build/+/master/masters/maste...

       'WebKit Linux (dbg)': 'swarming_gn_debug_bot_x64',
       'WebKit Linux ASAN': 'swarming_gn_asan_lsan_release_bot_x64',
       'WebKit Linux Leak': 'swarming_gn_release_bot_x64',
@@ -1297,10 +1297,6 @@
       'gyp', 'official', 'x64',
     ],
 
-    'gyp_release_bot_android': [
-      'gyp', 'release_bot', 'android',
-    ],
-
     'gyp_release_trybot': [
       'gyp', 'release_trybot',
     ],