Closed
Bug 1180063
Opened 9 years ago
Closed 6 years ago
transition remaining releng tools and services to gecko mozharness, and update mozharness docs
Categories
(Release Engineering :: Applications: MozharnessCore, defect)
Release Engineering
Applications: MozharnessCore
Tracking
(firefox42 fixed)
RESOLVED
FIXED
Tracking | Status | |
---|---|---|
firefox42 | --- | fixed |
People
(Reporter: jlund, Assigned: jlund)
References
Details
Attachments
(1 file)
1.68 KB,
patch
|
jlund
:
review+
|
Details | Diff | Splinter Review |
once all continuous integration jobs use in gecko tree mozharness, we will need to change how mapper and vcs-sync update themselves
in addition, we will also need to update docs to show how to obtain the latest copy of mozharness. This will be for use with push_apk, merges, etc
Assignee | ||
Comment 1•9 years ago
|
||
along with doc upgrades, mozharness's github, hg.m.o, and in-gecko-tree copy of README should also be updated to reflect the new changes
Assignee | ||
Updated•9 years ago
|
Summary: replace all releng deployment strategies and update docs of how to get latest copy of mozharness → transition remaining releng tools and services to gecko mozharness, and update mozharness docs
Assignee | ||
Comment 3•9 years ago
|
||
Attachment #8640619 -
Flags: review+
Assignee: nobody → jlund
Status: NEW → RESOLVED
Closed: 9 years ago
status-firefox42:
--- → fixed
Resolution: --- → FIXED
Assignee | ||
Updated•9 years ago
|
Assignee | ||
Comment 6•6 years ago
|
||
Not really. This is not applicable anymore or was done elsewhere.
Status: REOPENED → RESOLVED
Closed: 9 years ago → 6 years ago
Flags: needinfo?(jlund)
Resolution: --- → FIXED
Updated•6 years ago
|
Keywords: leave-open
You need to log in
before you can comment on or make changes to this bug.
Description
•