Closed
Bug 795774
Opened 12 years ago
Closed 12 years ago
Maintaining "latest" mobile symlinks on ftp.mozilla.org (release and beta)
Categories
(Release Engineering :: Release Automation: Other, defect, P2)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: francois, Assigned: nthomas)
Details
Attachments
(1 file, 1 obsolete file)
1.11 KB,
patch
|
mozilla
:
review+
nthomas
:
checked-in+
|
Details | Diff | Splinter Review |
Background: I noticed that the version of Firefox Beta that was available from http://f-droid.org/wiki/page/org.mozilla.firefox_beta was out of date and pinged the f-droid developers on IRC. What I found out is that upstream developers don't upload to the f-droid market directly. Instead, it's like a Linux distro: the f-droid developers / maintainers build and upload new APKs and they get published on that market. For most of the software, they watch the source code repositories directly and build+sign the APKs themselves. In the case of Firefox, it's not built from source for technical reasons but instead they download and republish our APKs. That fetch+republish process is manual at the moment because they don't have a good way of identifying the latest APKs on our ftp site. There is no "latest-beta" symlink for Android and the one for release is out of date: ftp://ftp.mozilla.org/pub/mozilla.org/mobile/releases/latest/android/multi/ If we could enable them to automatically fetch the right one, I imagine this would go a long way towards making sure that Firefox and Firefox Beta are kept up to date on that market. Request: On ftp://ftp.mozilla.org/pub/mozilla.org/mobile/releases/ : 1- making sure that the "latest" symlink is up to date after each Android release 2- adding a new "latest-beta" symlink These symlinks should point to the APKs that are currently available on Google Play.
Assignee | ||
Updated•12 years ago
|
Component: Release Engineering → Release Engineering: Automation (Release Automation)
QA Contact: bhearsum
Assignee | ||
Updated•12 years ago
|
Assignee: nobody → nthomas
Priority: -- → P2
Assignee | ||
Comment 1•12 years ago
|
||
Tested on dev-stage01. I'll need to create latest-beta symlink before we run this the first time in anger.
Attachment #671275 -
Flags: review?(aki)
Assignee | ||
Updated•12 years ago
|
Attachment #671275 -
Attachment description: [braindump] → [braindump] Update symlinks after push
Assignee | ||
Comment 2•12 years ago
|
||
Leaving out the stray mod in my braindump repo.
Attachment #671275 -
Attachment is obsolete: true
Attachment #671275 -
Flags: review?(aki)
Attachment #671276 -
Flags: review?(aki)
Comment 3•12 years ago
|
||
Comment on attachment 671276 [details] [diff] [review] [braindump] Update symlinks after push I suppose my only concern is if we go to a beta 10. Hopefully we'll have an automated push by then?
Attachment #671276 -
Flags: review?(aki) → review+
Assignee | ||
Comment 4•12 years ago
|
||
I checked b10 or higher will be OK too, as it's not matching on the end of the string. FTR, not a real regexp either, just bash's pattern matching that's kinda similar but not really.
Assignee | ||
Comment 5•12 years ago
|
||
Comment on attachment 671276 [details] [diff] [review] [braindump] Update symlinks after push http://hg.mozilla.org/build/braindump/rev/87a8fe7c6c53 And created latest-beta on ftp.m.o. dev-stage01 doesn't have a mobile/releases, but if it ever gets one we can add an |if [ -e $LATEST ]| around the rm.
Attachment #671276 -
Flags: checked-in+
Assignee | ||
Updated•12 years ago
|
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Comment 6•12 years ago
|
||
francois: can you get back to the f-droid team and tell them about this, so they can incorporate it into their process? Thanks, Gerv
Reporter | ||
Comment 7•12 years ago
|
||
Gerv: I pinged one of the main developers on IRC yesterday and he was happy to hear this. Thanks Nick!
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•