Closed Bug 1545109 Opened 5 years ago Closed 5 years ago

batch theme resigning with AMO

Categories

(Cloud Services :: Operations: Autograph, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: u581815, Unassigned)

Details

Per chat:

eviljeff> g-k: advance heads-up - AMO will be repacking and signing a large bunch (up to 500k) of themes towards the end of the April.

Also, per email from Shell and Dan we're potentially blocking the webext migration to COSE so we could resign those too while we're scaled up.

Type: defect → task

The theme resigning needs to be done for Fx 69.

Tentatively scheduled to kick this off next Tuesday (April 23rd).

Tentatively scheduled to kick this off next Tuesday (April 23rd).

For themes, the task will be available to run on prod after April 25th (Thursday). I'm going to start testing on addons-dev later this week and, if there are no problems found, continue to test on stage after the next tag on April 23rd. If we repack all of the stage themes then it depends on the speed of stage signing for how soon after the 23rd we'll be ready to execute on AMO production.

I don't know if there is code we need to land to allow resigning of webextensions in general (cgrebs probably knows most about this).

(In reply to Andrew Williamson [:eviljeff] from comment #2)

Tentatively scheduled to kick this off next Tuesday (April 23rd).

For themes, the task will be available to run on prod after April 25th (Thursday). I'm going to start testing on addons-dev later this week and, if there are no problems found, continue to test on stage after the next tag on April 23rd. If we repack all of the stage themes then it depends on the speed of stage signing for how soon after the 23rd we'll be ready to execute on AMO production.

Got it. Rescheduled for next Friday to run over the weekend.

I don't know if there is code we need to land to allow resigning of webextensions in general (cgrebs probably knows most about this).

OK pending feedback from :cgrebs on how difficult it'll be to do that around the same time as the theme resigning I might break that out into a separate bug.

OK pending feedback from :cgrebs on how difficult it'll be to do that around the same time as the theme resigning I might break that out into a separate bug.

I think it would be good to split out the re-signing of web-ext to a different bug since the timelines are independent, and we're going to be waiting on unlisted devs manually carrying out re-signing as well.

(In reply to Stuart Colville [:scolville] [:muffinresearch] from comment #4)

OK pending feedback from :cgrebs on how difficult it'll be to do that around the same time as the theme resigning I might break that out into a separate bug.

I think it would be good to split out the re-signing of web-ext to a different bug since the timelines are independent, and we're going to be waiting on unlisted devs manually carrying out re-signing as well.

Yep, opened https://bugzilla.mozilla.org/show_bug.cgi?id=1546399 for the web-ext resigning.

Summary: batch theme and webext resigning with AMO → batch theme resigning with AMO

Got it. Rescheduled for next Friday to run over the weekend.

It won't be run until Monday (or Tuesday) now, but stage testing indicates the first pass will only take about 12 hours anyway (and a few hours more for retries)

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