Closed Bug 1110769 Opened 11 years ago Closed 11 years ago

Schedule Linux64 code coverage builds and tests on Try as a non-default option

Categories

(Release Engineering :: General, defect)

x86_64
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: ahal, Assigned: ahal)

References

Details

Attachments

(1 file)

Non default means it will only show up on a try push if explicitly listed, it won't show up if 'all' is used. Historically we've used Cedar for standing up new builds and tests. This was so we could stage mozharness changes without needing to land changes in production and break all the other branches. Thanks to Armen, we can now push to Try with custom mozharness repos. This basically makes Cedar obsolete as standing up new builds/tests on Try is much nicer. For my own sanity, I'd like to schedule code coverage builds there so I can stop working on Cedar. It will also make it easier for other people to get coverage data (once that part is finished) for specific jobs/suites.
As usual, I'm not entirely sure this is going to do what I want. So I'll be explicit :). This patch is intended to: 1) Schedule linux64-cc builds and tests on Try. 2) Don't schedule builds by default so it doesn't get run by 'all' (I believe this is accomplished by 'try_by_default'=False which was already set). Tests should be scheduled by default if the build is run. 3) Stop scheduling them on Cedar, to save some resources. I'm assuming this will automatically get picked up by try syntax as 'linux64-cc'? Or is there another step I need to accomplish this?
Assignee: nobody → ahalberstadt
Status: NEW → ASSIGNED
Attachment #8535630 - Flags: review?(jlund)
Comment on attachment 8535630 [details] [diff] [review] Schedule linux64-cc on Try instead of Cedar Review of attachment 8535630 [details] [diff] [review]: ----------------------------------------------------------------- thanks for the explicit explanation of what you're hoping this achieves. lgtm :) I don't think we can really test this but based upon what I can tell, this should do what you want.
Attachment #8535630 - Flags: review?(jlund) → review+
Attachment #8535630 - Flags: checked-in+
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: