[android-components] add independent nightly releases to compete with snapshots
Categories
(Release Engineering :: General, task)
Tracking
(Not tracked)
People
(Reporter: mtabara, Assigned: mtabara)
References
(Blocks 1 open bug)
Details
Attachments
(9 files, 1 obsolete file)
62 bytes,
text/x-github-pull-request
|
Details | Review | |
62 bytes,
text/x-github-pull-request
|
Details | Review | |
47 bytes,
text/x-phabricator-request
|
Details | Review | |
62 bytes,
text/x-github-pull-request
|
Details | Review | |
63 bytes,
text/x-github-pull-request
|
Details | Review | |
60 bytes,
text/x-github-pull-request
|
Details | Review | |
62 bytes,
text/x-github-pull-request
|
Details | Review | |
62 bytes,
text/x-github-pull-request
|
Details | Review | |
62 bytes,
text/x-github-pull-request
|
Details | Review |
We're currently investigating whether we can switch off AC snapshots and instead built nightlies (which are regular Github releases happening twice a day, with a "buildid" instead of "snapshot").
This should help with reproducible builds and eliminating the caching issues as the current snapshots overlap in the latest locations in maven.mozilla.org.
Assignee | ||
Updated•5 years ago
|
Assignee | ||
Comment 1•5 years ago
|
||
Assignee | ||
Comment 2•5 years ago
|
||
Assignee | ||
Comment 3•5 years ago
|
||
Updated•5 years ago
|
Assignee | ||
Comment 4•5 years ago
|
||
Updated•5 years ago
|
Assignee | ||
Comment 5•5 years ago
|
||
Assignee | ||
Updated•5 years ago
|
Assignee | ||
Comment 6•5 years ago
|
||
Assignee | ||
Comment 7•5 years ago
|
||
I have updated SOPS as well with the credentials.
Assignee | ||
Comment 8•5 years ago
|
||
Assignee | ||
Comment 9•5 years ago
|
||
Nightly graphs successfully pushed to the S3 upload buckets - https://firefox-ci-tc.services.mozilla.com/tasks/groups/S_NqnH8ZRky3MY7ucv3n_g
So we upload correctly, but we have some issues with the lamda workers not replicating the data or the serving bucket being misconfigured. Either way, we're very close to victory.
Assignee | ||
Comment 10•5 years ago
|
||
Aaaaand ... we're live: https://nightly.maven.mozilla.org/?prefix=maven2/org/mozilla/components/
Assignee | ||
Comment 11•5 years ago
|
||
Assignee | ||
Comment 12•5 years ago
|
||
Assignee | ||
Comment 13•5 years ago
|
||
Assignee | ||
Comment 14•5 years ago
|
||
https://firefox-ci-tc.services.mozilla.com/tasks/groups/H8ln-zW0T8-nL07WZ4iItg looks good, with the pom files pointing at the right versions finally.
Assignee | ||
Comment 15•5 years ago
|
||
Nightlies looking good but we now have a problem with lambda workers. E.g. https://nightly.maven.mozilla.org/maven2/org/mozilla/components/browser-session/maven-metadata.xml was giving different results to me vs Sebastian.
Plan of action:
- nuke everything up in the nightly MMO buckets + clear the caches
- push a fresh new AC nightly
- check the logs for lambda workers and spot the problem
- fix and deploy the lambda workers
- celebrate
Assignee | ||
Comment 16•5 years ago
|
||
(In reply to Mihai Tabara [:mtabara]⌚️GMT from comment #15)
Nightlies looking good but we now have a problem with lambda workers. E.g. https://nightly.maven.mozilla.org/maven2/org/mozilla/components/browser-session/maven-metadata.xml was giving different results to me vs Sebastian.
Plan of action:
- nuke everything up in the nightly MMO buckets + clear the caches
DONE
- push a fresh new AC nightly
DONE - latest release is https://firefox-ci-tc.services.mozilla.com/tasks/groups/OZWTUfrITIaANMK3XqgUuQ
published under nightly.maven.mozilla.org
on to debug lambda workers.
Assignee | ||
Comment 17•5 years ago
|
||
After the big nuke, things seem to be fine. I double-check with latest nightly earlier today, the ones at 13 UTC.
I think we can declare victory here.
:Sebastian and Johan have a plan to gradually roll this out - they are pinning the nightly version RB first and then consequently in Fenix in bug 1620190 via automation.
Let's declare victory here and re-surface if issues come up along the way.
Comment hidden (collapsed) |
Description
•