Closed Bug 1171632 Opened 5 years ago Closed 4 years ago

Migrate Hazard builds to TaskCluster

Categories

(Release Engineering :: General, defect)

defect
Not set

Tracking

(firefox49 fixed)

RESOLVED FIXED
Tracking Status
firefox49 --- fixed

People

(Reporter: coop, Assigned: sfink)

References

Details

Attachments

(2 files)

If these already have a mozharness script then they ought to be easy enough to run in desktop-build, since the build-linux.sh script that invokes the Linux/Mac desktop builds is actually just a mostly-generic mozharness invocation:
https://dxr.mozilla.org/mozilla-central/source/testing/taskcluster/scripts/builder/build-linux.sh#115

You just need a task definition that specifies the right mozharness bits:
https://dxr.mozilla.org/mozilla-central/source/testing/taskcluster/tasks/builds/linux64_clobber.yml#26
Hm, I thought I'd already done this, but I guess not.

This patch moves the hazard builds from the try branch to the base jobs file. I believe that should run them everywhere-ish.

https://treeherder.mozilla.org/#/jobs?repo=try&revision=df7a9db0a3b18048183276766198b97779e4ff34 proves that I haven't broken them yet.

Once these go live, we can turn off the buildbot ones. I'll email sheriffs.

MozReview-Commit-ID: 9yT79JaguUc
Attachment #8745574 - Flags: review?(coop)
Assignee: nobody → sphink
Status: NEW → ASSIGNED
And here's the patch to kill off the buildbot jobs, which I'll land after the new TC jobs show up.
Attachment #8745580 - Flags: review?(coop)
Attachment #8745574 - Flags: review?(coop) → review+
Attachment #8745580 - Flags: review?(coop) → review+
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.