Closed
Bug 1042829
Opened 10 years ago
Closed 10 years ago
Update Android SDK and build tools to 20
Categories
(Infrastructure & Operations Graveyard :: CIDuty, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: wesj, Assigned: wesj)
References
Details
Attachments
(1 file)
(deleted),
patch
|
Details | Diff | Splinter Review |
While fixing bug 1016529, I noticed sdk 20 is out now. We have a few features that need 19+ (stumbler and restricted profiles), and once we know an sdk works, we should keep ourselves up to date.
I have new found tool-tool powers that I seem to finally be able to use, so I can do this for releng if they're ok with it (with reviews going to them).
Comment 1•10 years ago
|
||
Bug 1030265 covers raising our target SDK version. We'll also want to do something like Bug 1024238 to die early for outdated tools.
Blocks: 1030265
OS: Linux → Android
Hardware: x86_64 → All
Summary: Updated android sdk to 20 → Update Android SDK and build tools to 20
Assignee | ||
Comment 2•10 years ago
|
||
I pushed this up to tooltool. Here are the manifest entries. Waiting on a try run https://tbpl.mozilla.org/?tree=Try&rev=291ace64c568
Assignee | ||
Comment 3•10 years ago
|
||
And I didn't update the version code in mozconfig. Lets try again:
https://tbpl.mozilla.org/?tree=Try&rev=bf00cfc3dd30
Assignee | ||
Comment 4•10 years ago
|
||
We're hitting strange errors in proguard. rnewman hinted that they may be due to jdk1.6 (at least, he's seen them with Java6).
Depends on: 1043023
Comment 5•10 years ago
|
||
That's bug 951968.
Comment 6•10 years ago
|
||
This can't come soon enough; just hit another thing that KitKat broke for which the fix is only available in 19+.
https://tbpl.mozilla.org/php/getParsedLog.php?id=45296026&tree=Fx-Team
Assignee | ||
Comment 7•10 years ago
|
||
Trying again:
https://tbpl.mozilla.org/?tree=Try&rev=8a1c188388ec
Assignee | ||
Comment 8•10 years ago
|
||
Whoops. Had to update mozconfig.common as well. Try again:
https://tbpl.mozilla.org/?tree=Try&rev=59f57d37778e
Assignee | ||
Comment 9•10 years ago
|
||
I was apparently at a bad revision for that push. Pulled. Lets try again:
https://tbpl.mozilla.org/?tree=Try&rev=59f57d37778e
Assignee | ||
Comment 10•10 years ago
|
||
Looked good. Landed on fx-team:
https://hg.mozilla.org/integration/fx-team/rev/b9fc8a08a0c2
Backed out in https://hg.mozilla.org/integration/fx-team/rev/9fa6759714ac under suspicion of causing various android failures in the following push.
https://tbpl.mozilla.org/php/getParsedLog.php?id=45973080&tree=Fx-Team
https://tbpl.mozilla.org/php/getParsedLog.php?id=45975386&tree=Fx-Team
https://tbpl.mozilla.org/php/getParsedLog.php?id=45976146&tree=Fx-Team
https://tbpl.mozilla.org/php/getParsedLog.php?id=45974436&tree=Fx-Team
Though nalexander thinks it's more likely Bug 1052276 that could be the cause of at least some of these.
Flags: needinfo?(wjohnston)
Relanded in https://hg.mozilla.org/integration/fx-team/rev/e0c877dfa4da since 1052276 seems more likely at this point.
Flags: needinfo?(wjohnston)
Comment 13•10 years ago
|
||
Assignee: nobody → wjohnston
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Updated•7 years ago
|
Component: Platform Support → Buildduty
Product: Release Engineering → Infrastructure & Operations
Updated•5 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•