Closed Bug 978510 Opened 11 years ago Closed 8 years ago

port mozharness desktop build cfgs from mozharness to in-tree

Categories

(Release Engineering :: Applications: MozharnessCore, defect)

Product:
Release Engineering
Component:
Applications: MozharnessCore
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: jlund, Assigned: jlund)

References

Details

(Whiteboard: [mozharness])

No description provided.
Depends on: 978513
Depends on: 978211
Component: General Automation → Mozharness
Now that mozharness is in-tree, is this still relevant? This is referenced by [1] but I presume that maintaining things like this make it slightly easier to handle cross-branch merges. [1] https://dxr.mozilla.org/mozilla-central/rev/b056526be38e96b3e381b7e90cd8254ad1d96d9d/testing/mozharness/configs/builds/branch_specifics.py#4-5
Yeah, iirc, this was filed before all the configs and mozharness itself went in tree. Fixed!
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.