Closed
Bug 1186883
Opened 9 years ago
Closed 9 years ago
Update aurora android single-locale configs to remove setup.sh
Categories
(Release Engineering :: Applications: MozharnessCore, defect)
Release Engineering
Applications: MozharnessCore
Tracking
(firefox42 fixed)
RESOLVED
FIXED
Tracking | Status | |
---|---|---|
firefox42 | --- | fixed |
People
(Reporter: mshal, Assigned: mshal)
References
Details
Attachments
(3 files)
3.53 KB,
patch
|
jlund
:
review+
|
Details | Diff | Splinter Review |
6.98 KB,
patch
|
jlund
:
review+
|
Details | Diff | Splinter Review |
10.53 KB,
patch
|
jlund
:
review+
|
Details | Diff | Splinter Review |
setup.sh was removed in bug 1182407, but the android single-locale mozharness configs still try to use it. This was fixed for the mozilla-central configs in bug 1186243, but we'll need to update the aurora versions during uplift.
Assignee | ||
Comment 1•9 years ago
|
||
Attachment #8638032 -
Flags: review?(jlund)
Assignee | ||
Comment 2•9 years ago
|
||
Attachment #8638033 -
Flags: review?(jlund)
Assignee | ||
Comment 3•9 years ago
|
||
Once we get to release, we can kill the bootstrap_cmd argument in tooltool_fetch().
Attachment #8638034 -
Flags: review?(jlund)
Updated•9 years ago
|
Attachment #8638032 -
Flags: review?(jlund) → review+
Updated•9 years ago
|
Attachment #8638033 -
Flags: review?(jlund) → review+
Updated•9 years ago
|
Attachment #8638034 -
Flags: review?(jlund) → review+
Assignee | ||
Comment 4•9 years ago
|
||
:jlund, are we still trying to maintain parity with the in-tree mozharness and build/mozharness? Or are we settled into in-tree mozharness as RoR and build/mozharness is no longer needed? I need to land the aurora patch for the uplift, but it would be nice to be able to land the beta+release patches into m-c now so they ride appropriately. Otherwise I'll have to land the beta patch into aurora before the next uplift, I think.
Flags: needinfo?(jlund)
Comment 5•9 years ago
|
||
(In reply to Michael Shal [:mshal] from comment #4) > :jlund, are we still trying to maintain parity with the in-tree mozharness > and build/mozharness? Or are we settled into in-tree mozharness as RoR and > build/mozharness is no longer needed? > > I need to land the aurora patch for the uplift, but it would be nice to be > able to land the beta+release patches into m-c now so they ride > appropriately. Otherwise I'll have to land the beta patch into aurora before > the next uplift, I think. we are settled and will not be rolling back to build/mozharness. build/mozharness can still be written to at this point but it is not necessary
Flags: needinfo?(jlund)
https://hg.mozilla.org/integration/mozilla-inbound/rev/1ada2f33f5a8 https://hg.mozilla.org/integration/mozilla-inbound/rev/b72fbba8e4d1 https://hg.mozilla.org/integration/mozilla-inbound/rev/eaba8bf91ec9
https://hg.mozilla.org/mozilla-central/rev/1ada2f33f5a8 https://hg.mozilla.org/mozilla-central/rev/b72fbba8e4d1 https://hg.mozilla.org/mozilla-central/rev/eaba8bf91ec9
Assignee: nobody → mshal
Status: NEW → RESOLVED
Closed: 9 years ago
status-firefox42:
--- → fixed
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•