B2G doesn't have addon support anyway, so besides giving us random failures to star from time to time, they're doing nothing but wasting CPU cycles. We should shut them off.
Good spot :-)
Given that our oldest supported Gecko rev is 24 at this point, I think we can just alter the below line to exclude branches starting with "mozilla-b2g". Otherwise, a hard-coded list I guess. https://mxr.mozilla.org/build/source/buildbot-configs/mozilla-tests/config.py#1704
Which line 1853 already shows exactly how to do! for name in [x for x in BRANCHES.keys() if x.startswith('mozilla-b2g')]:
Created attachment 8463728 [details] [diff] [review] patch I think this is what we want. The comment on the line above says what I'm attempting to accomplish here. I only want to schedule Jetpack tests if the branch doesn't start with mozilla-b2g.
Assignee: nobody → ryanvm
Status: NEW → ASSIGNED
Attachment #8463728 - Flags: review?(catlee)
Comment on attachment 8463728 [details] [diff] [review] patch https://hg.mozilla.org/build/buildbot-configs/rev/336cc1dd364b
Attachment #8463728 - Flags: checked-in+
Comment on attachment 8463728 [details] [diff] [review] patch Backed out for releng-ci failures. http://hg.mozilla.org/build/buildbot-configs/rev/83be930dee2b INFO - ValueError: duplicate builder name Ubuntu VM 12.04 x64 mozilla-inbound opt test jetpack
Attachment #8463728 - Flags: checked-in+ → checked-in-
Created attachment 8464149 [details] [diff] [review] patch v2 Don't let branch get stale
Comment on attachment 8464149 [details] [diff] [review] patch v2 Second time lucky! https://hg.mozilla.org/build/buildbot-configs/rev/87e79909a672
Attachment #8464149 - Flags: checked-in+
something(s) here went to production today
Confirmed that JP jobs are no longer starting on mozilla-b2g* for new pushes.
Status: ASSIGNED → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
Component: General Automation → General
Product: Release Engineering → Release Engineering
You need to log in before you can comment on or make changes to this bug.