Add new site isolation trybot.

masters/master.tryserver.chromium.linux/master.cfg

Index: masters/master.tryserver.chromium.linux/master.cfg
diff --git a/masters/master.tryserver.chromium.linux/master.cfg b/masters/master.tryserver.chromium.linux/master.cfg
index 9875cf4867adbcc14042afd5020a4681b88c4d58..8a06d14c8e5c9977970f2c5af77e68aa2a6500ca 100644
--- a/masters/master.tryserver.chromium.linux/master.cfg
+++ b/masters/master.tryserver.chromium.linux/master.cfg
@@ -263,6 +263,13 @@ b_linux_chromium_asan_rel = {
   'slavebuilddir': 'linux_asan',
 }
 
+b_linux_site_isolation = {
+  'name': 'linux_site_isolation',
+  'factory': m_annotator.BaseFactory('chromium_trybot'),
+  # Share build directory with compatible existing builders to save space.

[hinoka, 2015/02/21 01:29:11]

Remove this comment, its not actually true in this case :P

[alexmos, 2015/02/21 01:52:57]

Comment removed.  Thinking about this though, our bot doesn't need any special
build flags; the only difference from regular trybots is passing a runtime flag
--site-per-process to the test binaries.  So, do we actually want to use a new
build dir for our bot?

[hinoka, 2015/02/24 19:49:31]

Hm you're right.  Maybe its okay to share with the linux (or other) folder if
you can confirm they have the same build flags.  You should be able to glean
that from the expectations.

+  'slavebuilddir': 'linux_site_isolation',
+}
+
 b_linux_chromium_asan_rel_ng = {
   'name': 'linux_chromium_asan_rel_ng',
   'factory': m_annotator.BaseFactory('chromium_trybot'),
@@ -405,6 +412,7 @@ c['builders'] = [
   b_linux_full_bisect_builder,
   b_linux_nacl_sdk, b_linux_nacl_sdk_bionic,
   b_linux_nacl_sdk_build, b_linux_nacl_sdk_bionic_build,
+  b_linux_site_isolation,
   b_chromium_presubmit,
   b_tools_build_presubmit,
   b_infra_tester,