Create recipe to run find_annotated_tests.py periodically

masters/master.chromium.infra.cron/master.cfg

Index: masters/master.chromium.infra.cron/master.cfg
diff --git a/masters/master.chromium.infra.cron/master.cfg b/masters/master.chromium.infra.cron/master.cfg
index 8437cb217962ea6b99fdd6f4231e9f19ddc0f23a..51e2f80b269f77c8cbd64cdb1944c3111a5a86ea 100644
--- a/masters/master.chromium.infra.cron/master.cfg
+++ b/masters/master.chromium.infra.cron/master.cfg
@@ -156,6 +156,10 @@ c['builders'].extend([
     'category': '1cron',
   },
   {
+    'name': 'Chromium Android Find Annotated Test',

[jbudorick, 2016/06/20 09:28:26]

What's your reasoning behind putting this on chromium.infra.cron?

[the real yoland, 2016/06/21 23:16:08]

Because I thought all the timely scheduled jobs belongs to this master (with the
word cron)

[jbudorick, 2016/06/22 10:21:37]

No, that's definitely not the case. This is specifically for infra tasks, and I
don't think this qualifies. I think a new section in chromium.android is a
better fit.

+    'factory': f_annotations.BaseFactory(recipe='find_annonated_tests'),
+    'category': '1cron',
+  {
     'name': 'Chromium Linux Codesearch',
     'factory': f_annotations.BaseFactory(recipe='chromium_codesearch'),
     'category': '2codesearch',
@@ -213,6 +217,12 @@ c['schedulers'].extend([
       hour=range(0, 24, 4),
       minute=0,
       builderNames=['Chromium Linux Codesearch', 'ChromiumOS Codesearch']),
+  Nightly(
+      name='find_annotated_tests',
+      branch='master',
+      hour=range(0, 24, 4),
+      minute=0,
+      builderNames=['Chromium Android Find Annotated Tests']),
 
   # Trigger this builder on any change anywhere.
   AnyBranchScheduler(