Closed Bug 1615248 Opened 2 years ago Closed 2 years ago

[android-components] add independent nightly releases to compete with snapshots

Categories

(Release Engineering :: General, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

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.

Summary: investigate the replacement of AC snapshots with nightlies → [android-components] add independent nightly releases to compete with snapshots
Assignee: nobody → mtabara
Depends on: 1616304
See Also: → 1493942
Attachment #9127914 - Attachment description: Add initial resources for AC nightly → Bug 1615248 - Add initial resources for AC nightly. r=jlorenzo
Attachment #9127914 - Attachment is obsolete: true
Attachment #9128769 - Attachment description: [android-components] fixes build paths → [android-components] fixes build paths and adds signing

I have updated SOPS as well with the credentials.

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.

https://firefox-ci-tc.services.mozilla.com/tasks/groups/H8ln-zW0T8-nL07WZ4iItg looks good, with the pom files pointing at the right versions finally.

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:

  1. nuke everything up in the nightly MMO buckets + clear the caches
  2. push a fresh new AC nightly
  3. check the logs for lambda workers and spot the problem
  4. fix and deploy the lambda workers
  5. celebrate

(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:

  1. nuke everything up in the nightly MMO buckets + clear the caches

DONE

  1. 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.

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.

Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Blocks: 1620585
Blocks: 1639133
You need to log in before you can comment on or make changes to this bug.