Bug 1382729: add support for run-on-projects with -j; r?gps draft
authorDustin J. Mitchell <dustin@mozilla.com>
Wed, 02 Aug 2017 17:11:59 +0000
changeset 619813 441840570e751db5f26dde9fa2e7da986f173339
parent 619812 c3ef4ec15ecd4fa0ec0b5af7aacddfa8d6dd90e0
child 641012 636e1631c92bee19a2e5aeaef66750f919bb0021
push id71827
push userdmitchell@mozilla.com
push dateWed, 02 Aug 2017 17:13:31 +0000
Bug 1382729: add support for run-on-projects with -j; r?gps MozReview-Commit-ID: GB5E5RhEcu
--- a/taskcluster/taskgraph/try_option_syntax.py
+++ b/taskcluster/taskgraph/try_option_syntax.py
@@ -598,17 +598,17 @@ class TryOptionSyntax(object):
                 # they will schedule their builds even if they end up optimized away. This means
                 # to run these tasks on try, they'll need to be explicitly specified by -j until
                 # we find a better solution (see bug 1372510).
                 return False
             elif not self.jobs and attr('build_platform'):
                 if self.platforms is None or attr('build_platform') in self.platforms:
                     return True
                 return False
-            return True
+            return check_run_on_projects()
         elif attr('kind') == 'test':
             return match_test(self.unittests, 'unittest_try_name') \
                  or match_test(self.talos, 'talos_try_name')
         elif attr('kind') in BUILD_KINDS:
             if attr('build_type') not in self.build_types:
                 return False
             elif self.platforms is None:
                 # for "-p all", look for try in the 'run_on_projects' attribute