Closed
Bug 1122076
Opened 10 years ago
Closed 10 years ago
Update the push_apk.py script to manage the new APK filenames
Categories
(Release Engineering :: Release Automation: Other, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: Sylvestre, Assigned: Sylvestre)
References
Details
Attachments
(1 file, 1 obsolete file)
(deleted),
patch
|
bhearsum
:
review+
Sylvestre
:
checked-in+
|
Details | Diff | Splinter Review |
For now, the push_apk script ( https://hg.mozilla.org/build/mozharness/file/28e050ccc2aa/scripts/push_apk.py ) expect two arguments:
--apk-x86 fennec-34.0b8.multi.android-i386.apk --apk-armv7 fennec-34.0b8.multi.android-arm.apk
This won't work with the new apk filenames.
The args should be renamed for something like;
--apk-armv7-v9
--apk-armv7-v11
etc
Assignee | ||
Comment 1•10 years ago
|
||
I am going to take care of this bug or mentor someone.
Comment 2•10 years ago
|
||
Following the CS dictum of "once you generalize from 1 to 2, you should generalize to N", you might want to consider a different approach altogether, and have this driven by a manifest.
Mentor: sledru
Summary: Update the push_apk.sh script to manage the new apk filenames → Update the push_apk.sh script to manage the new APK filenames
Whiteboard: good first bug → [good first bug]
Assignee | ||
Comment 3•10 years ago
|
||
(In reply to Richard Newman [:rnewman] from comment #2)
> Following the CS dictum of "once you generalize from 1 to 2, you should
> generalize to N", you might want to consider a different approach
> altogether, and have this driven by a manifest.
Right, I reported bug 1122509 for this (I haven't been able to find one)
Comment 4•10 years ago
|
||
(In reply to Sylvestre Ledru [:sylvestre] from comment #0)
> For now, the push_apk script (
> https://hg.mozilla.org/build/mozharness/file/28e050ccc2aa/scripts/push_apk.
> py ) expect two arguments:
> --apk-x86 fennec-34.0b8.multi.android-i386.apk --apk-armv7
> fennec-34.0b8.multi.android-arm.apk
>
> This won't work with the new apk filenames.
> The args should be renamed for something like;
> --apk-armv7-v9
> --apk-armv7-v11
> etc
Hello :sylvestre, so currently in push_apk.py script I see two options: --apk-armv7 and --apk-armv6. I'm wondering if you meant to prefix these two with v9 and v11 respectively until a manifest solution is worked out? Let me know if that was the intention and I can submit a patch for this.
Flags: needinfo?(sledru)
Assignee | ||
Comment 5•10 years ago
|
||
(In reply to Simarpreet Singh from comment #4)
> (In reply to Sylvestre Ledru [:sylvestre] from comment #0)
> Hello :sylvestre, so currently in push_apk.py script I see two options:
> --apk-armv7 and --apk-armv6. I'm wondering if you meant to prefix these two
> with v9 and v11 respectively until a manifest solution is worked out? Let me
> know if that was the intention and I can submit a patch for this.
No, prefixing won't work since we expect to have more and more apks in the future.
So, we are going to use a manifest file for this but I don't think it has been implemented yet (cf bug 1122509).
I am going to remove the good first bug since it is not ready yet. Sorry about that.
Mentor: sledru
Flags: needinfo?(sledru)
Whiteboard: [good first bug]
Updated•10 years ago
|
Component: Other → Release Automation
QA Contact: pmoore → bhearsum
Comment 6•10 years ago
|
||
like 1122071, afaik, push_apk.sh is managed by relman these days.
Sylvestre, do you need a hand adjusting the script to support new split apk file names or are you happy to continue mentoring/finishing this yourself? Let me know if I can assist in something here from releng side of things.
Assignee | ||
Comment 7•10 years ago
|
||
I am happy to do it myself (or mentor it) once the manifest is there! :)
Thanks for the offer!
Assignee | ||
Comment 8•10 years ago
|
||
Because we don't have a manifest (yet?), because we have now 3 apks instead of 2, I am going to be lazy and have two arguments for armv7 apk.
We need that stuff to land and we cannot wait for bug 1122509.
Attachment #8573338 -
Flags: review?(bhearsum)
Assignee | ||
Comment 9•10 years ago
|
||
Looks like I did a mistake in the export of the patch. Fixed!
Attachment #8573338 -
Attachment is obsolete: true
Attachment #8573338 -
Flags: review?(bhearsum)
Attachment #8573341 -
Flags: review?(bhearsum)
Updated•10 years ago
|
Attachment #8573341 -
Flags: review?(bhearsum) → review+
Assignee | ||
Comment 10•10 years ago
|
||
Comment on attachment 8573341 [details] [diff] [review]
bug_1122076.diff
https://hg.mozilla.org/build/mozharness/rev/6ece356e4c17
Attachment #8573341 -
Flags: checked-in+
Assignee | ||
Comment 11•10 years ago
|
||
That works (tested with the last beta)
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•10 years ago
|
Summary: Update the push_apk.sh script to manage the new APK filenames → Update the push_apk.py script to manage the new APK filenames
Assignee | ||
Updated•10 years ago
|
Assignee: nobody → sledru
You need to log in
before you can comment on or make changes to this bug.
Description
•