Closed Bug 1464816 Opened 2 years ago Closed 2 years ago

Automated pinning updates aren't running on ESR60

Categories

(Release Engineering :: Release Automation: Other, enhancement)

enhancement
Not set

Tracking

(firefox-esr60 fixed, firefox61 fixed, firefox62 fixed)

RESOLVED FIXED
Tracking Status
firefox-esr60 --- fixed
firefox61 --- fixed
firefox62 --- fixed

People

(Reporter: RyanVM, Assigned: sfraser)

References

Details

Attachments

(1 file)

We need the automated HSTS/HPKP/Blocklist updates to run on ESR60. Preferably once a week (daily is extreme overkill).
Assignee: nobody → sfraser
I've copied the m-c schedule, as the task sometimes
fails with timeouts. This does add to the releaseduty workload,
until automatic landing is operational.
jlund, are you ok with the extra work for releaseduty, here? Do we know when Lando's going to be ready yet?
Flags: needinfo?(jlund)
Comment on attachment 8981338 [details]
Bug 1464816 Run periodic file updates on mozilla-esr60 r=ryanvm

Ryan VanderMeulen [:RyanVM] has approved the revision.

https://phabricator.services.mozilla.com/D1438
Attachment #8981338 - Flags: review+
Pushed by sfraser@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/de8c8efbe24f
Run periodic file updates on mozilla-esr60 r=ryanvm
https://hg.mozilla.org/mozilla-central/rev/de8c8efbe24f
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
(In reply to Simon Fraser [:sfraser] ⌚️GMT from comment #2)
> jlund, are you ok with the extra work for releaseduty, here? Do we know when
> Lando's going to be ready yet?

Lando is planned to go live this week.

I saw similar patches to this last week but deferred to Mihai. It now makes more sense. At any rate, Is the idea to retry these if they fail and review and land once they are up on phabricator? How will releaseduty get notified? Better, how should we ensure this routine work gets done?
Flags: needinfo?(jlund) → needinfo?(sfraser)
The idea is indeed to retry, and people on releaseduty should get notified if the reviewers list is kept up to date. There's a note in https://github.com/mozilla-releng/releasewarrior-2.0/blob/master/docs/CHANGELOG.md#added-1 about where to modify that list.

Assuming the automatic landing tools arrive soon it's probably not worth putting too much into this, but if it looks like they'll be a while after Lando is first in production, then we should make sure it's on the checklists
Flags: needinfo?(sfraser)
(In reply to Simon Fraser [:sfraser] ⌚️GMT from comment #7)
> The idea is indeed to retry, and people on releaseduty should get notified
> if the reviewers list is kept up to date. There's a note in
> https://github.com/mozilla-releng/releasewarrior-2.0/blob/master/docs/
> CHANGELOG.md#added-1 about where to modify that list.
> 
> Assuming the automatic landing tools arrive soon it's probably not worth
> putting too much into this, but if it looks like they'll be a while after
> Lando is first in production, then we should make sure it's on the checklists

Got it thanks. Seems reasonable for releaseduty to manage until we integrate it with Lando.
You need to log in before you can comment on or make changes to this bug.