Closed
Bug 1297519
Opened 7 years ago
Closed 7 years ago
Generate multilocale Firefox snaps in beta
Categories
(Release Engineering :: Release Automation: Other, defect)
Release Engineering
Release Automation: Other
Tracking
(firefox51 fixed)
RESOLVED
FIXED
Tracking | Status | |
---|---|---|
firefox51 | --- | fixed |
People
(Reporter: rail, Assigned: rail)
References
Details
Attachments
(4 files, 1 obsolete file)
58 bytes,
text/x-review-board-request
|
jlorenzo
:
review+
rail
:
checked-in+
|
Details |
58 bytes,
text/x-review-board-request
|
jlorenzo
:
review+
rail
:
checked-in+
|
Details |
58 bytes,
text/x-review-board-request
|
Callek
:
review+
rail
:
checked-in+
|
Details |
48 bytes,
text/x-github-pull-request
|
rail
:
review+
rail
:
checked-in+
|
Details | Review |
Snaps should include all shipped locales. We can probably schedule only nightly CI and release tasks for these (because it would require to have all repacks and XPIs ready).
Assignee | ||
Updated•7 years ago
|
Assignee: nobody → rail
Summary: Generate multilocale Firefox snaps → Generate multilocale Firefox snaps in beta
Assignee | ||
Comment 1•7 years ago
|
||
The idea is have a docker image and a script to generate snap images. I put all related files into a single directory. We can either generate an image and publish it to dockerhub, or generate it runtime. There will be a task generating a snap and its checksum, a task signing the checksum, and a beetmover task to copy these to the candidates directory. Snaps will be enabled per branch (another branch config variable passed down to releasetasks). Something like this.
Attachment #8786073 -
Flags: feedback?(jlund)
Comment 2•7 years ago
|
||
Do we need to remove the firefox-l10n.js pref file that sets en-US? IIRC, the matchOS pref and the general.useragent.locale need both to be tweaked for matchOS to work.
Assignee | ||
Comment 3•7 years ago
|
||
I tested it and it works without any further customization, LANG=xx_YY /snap/bin/firefox works just fine.
Assignee | ||
Comment 4•7 years ago
|
||
The easiest way to test it is to run the following command and then install the generated snap file: docker run -e VERSION=49.0b7 -e BUILD_NUMBER=1 \ -e CANDIDATES_DIR=https://archive.mozilla.org/pub/firefox/candidates \ -v $(pwd):/snapcraft -v $(pwd)/home:/home \ -ti rail/snap-dev sh -c "cd /snapcraft && bash runme.sh" This will generate ./home/worker/artifacts/firexo*.snap, which can be installed by running sudo snap install ./home/worker/artifacts/firexo*.snap
Comment 5•7 years ago
|
||
Comment on attachment 8786073 [details] [diff] [review] snapcraft.diff from an overall approach perspective, this looks sane to me. ++ to having what you have defined in tree. we discussed over video of using hg.m.o subdir archive url locations for retrieving this since we only need to grab this once per release. have you tested this either through tc task creator yet? Locally maybe? Be cool to see inputs/outputs/logs for this.
Attachment #8786073 -
Flags: feedback?(jlund) → feedback+
Comment hidden (mozreview-request) |
Comment hidden (mozreview-request) |
Assignee | ||
Comment 8•7 years ago
|
||
There is nothing using this flags yet, but soon will be. Just need to land these before I can use them in releasetasks.
Comment 9•7 years ago
|
||
Comment on attachment 8791825 [details] Bug 1297519 - Generate multilocale Firefox snaps The changes in release-runner make sense to me.
Attachment #8791825 -
Flags: review?(jlorenzo) → review+
Comment 10•7 years ago
|
||
Comment on attachment 8791824 [details] Bug 1297519 - Generate multilocale Firefox snaps So do the variable initialization in buildbot-configs
Attachment #8791824 -
Flags: review?(jlorenzo) → review+
Assignee | ||
Comment 11•7 years ago
|
||
Comment on attachment 8791825 [details] Bug 1297519 - Generate multilocale Firefox snaps https://hg.mozilla.org/build/tools/rev/46ece28c68a5
Attachment #8791825 -
Flags: checked-in+
Assignee | ||
Comment 12•7 years ago
|
||
Comment on attachment 8791824 [details] Bug 1297519 - Generate multilocale Firefox snaps https://hg.mozilla.org/build/buildbot-configs/rev/4354ce6042f5
Attachment #8791824 -
Flags: checked-in+
Comment hidden (mozreview-request) |
Assignee | ||
Comment 14•7 years ago
|
||
The patch requires https://github.com/mozilla/releasetasks/compare/master...rail:snap?expand=1 to work. Tested on jamun, see https://treeherder.mozilla.org/#/jobs?repo=jamun&revision=c7f77d4cd7da9f8ee19eca47a67b565d0a9f6041&filter-searchStr=snap and the corresponding graphs.
Comment 15•7 years ago
|
||
mozreview-review |
Comment on attachment 8792039 [details] Bug 1297519 - Generate multilocale Firefox snaps , a=release DONTBUILD https://reviewboard.mozilla.org/r/79290/#review77838 I'm not too familair with snap/snapcraft, but the overall logic, while fragile, looks sane [and no less fragile than many of our other tooling in this area]. ::: release/docker/firefox-snap/Dockerfile:5 (Diff revision 1) > +FROM ubuntu:16.04 > + > +RUN apt-get update -q && apt-get install -qy software-properties-common && apt-get clean > +RUN add-apt-repository ppa:snappy-dev/snapcraft-daily > +RUN apt-get update && apt-get install -qy snapcraft bzip2 curl && apt-get clean not as enticed by a ppa for -dev/-daily and then installing that package without any sort of version pinning. Feels like we'd be asking for trouble on docker regens (since an unrelated change could take a newer unstable snapshot that breaks us). I won't block on this since we're still getting our feet wet here. :-) ::: release/docker/firefox-snap/Makefile:9 (Diff revision 1) > + > +build: > + docker build -t $(FULL_IMAGE_NAME) --no-cache --rm . > + > +push: > + docker push $(FULL_IMAGE_NAME):latest can we tag each push with some sort of buildID as well, so rollbacks are easy?
Attachment #8792039 -
Flags: review?(bugspam.Callek) → review+
Assignee | ||
Comment 16•7 years ago
|
||
(In reply to Justin Wood (:Callek) from comment #15) > not as enticed by a ppa for -dev/-daily and then installing that package > without any sort of version pinning. It needed this at some point to get latest snap/snapcraft. I can check if Ubuntu got the updates in the main repo, so we can get rid of the PPA. > can we tag each push with some sort of buildID as well, so rollbacks are > easy? We won't be using tags in any case (we use sha256). Pushing :latest is just faster (no need to push everything).
Comment hidden (mozreview-request) |
Assignee | ||
Comment 18•7 years ago
|
||
https://reviewboard.mozilla.org/r/79290/diff/1-2/ addresses the PPA comment
Comment 19•7 years ago
|
||
Pushed by raliiev@mozilla.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/4606672d8efe Generate multilocale Firefox snaps r=Callek, a=release DONTBUILD
Assignee | ||
Comment 20•7 years ago
|
||
Comment on attachment 8792039 [details] Bug 1297519 - Generate multilocale Firefox snaps , a=release DONTBUILD https://hg.mozilla.org/integration/mozilla-inbound/rev/4606672d8efe https://hg.mozilla.org/releases/mozilla-aurora/rev/79adb317eca4
Attachment #8792039 -
Flags: checked-in+
Comment 21•7 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/4606672d8efe
Assignee | ||
Comment 22•7 years ago
|
||
Forgot the magic words
Comment 23•7 years ago
|
||
In production: https://hg.mozilla.org/build/buildbot-configs/rev/4354ce6042f5
Assignee | ||
Comment 24•7 years ago
|
||
Attachment #8794390 -
Flags: review?(bugspam.Callek)
Assignee | ||
Updated•7 years ago
|
Attachment #8786073 -
Attachment is obsolete: true
Assignee | ||
Comment 25•7 years ago
|
||
Comment on attachment 8794390 [details] [review] PR for releasetasks r+ed in the PR
Attachment #8794390 -
Flags: review?(bugspam.Callek)
Attachment #8794390 -
Flags: review+
Attachment #8794390 -
Flags: checked-in+
Assignee | ||
Updated•7 years ago
|
Status: REOPENED → RESOLVED
Closed: 7 years ago → 7 years ago
Resolution: --- → FIXED
Updated•5 years ago
|
Keywords: leave-open
You need to log in
before you can comment on or make changes to this bug.
Description
•