Closed Bug 948335 Opened 6 years ago Closed 5 years ago

'ready to release' emails not being sent for release


(Release Engineering :: Release Automation: Other, defect, P2)



(Not tracked)



(Reporter: nthomas, Assigned: nthomas)


(Whiteboard: [kanban:engops:] )


(2 files)

The weights of the mirrors have changed a lot since the days when we had volunteers, but we still expect 45k uptake for release builds. These days we have a little over 10k for updates, and 2 million for installers. (IT does it this way to get the behavior we want from bouncer, rather than anything else).

We also don't need to make any distinction between uptake before notifying for 'ready for release' and 'ready to releasetest testing', since there is very short 'sync lag' between our CDN origin server and the CDN itself. Just 5 mins for the bouncer sentry to go around and request the files, and enable the CDN in bouncer.
See for the current weightings.
Attachment #8345199 - Flags: review?(catlee)
All these releases are the same from the point of view of serving them, CDN ftw.
Attachment #8345201 - Flags: review?(catlee)
It may be also related to bug 629648 and multiple reconfigs happened around that time.
Attachment #8345199 - Flags: review?(catlee) → review+
Attachment #8345201 - Flags: review?(catlee) → review+
I double checked emails for the last couple of cycles. We've gotten 'ready to release' builds for firefox esr17 and betas, where releasetestUptake was set to 1, and releaseUptake to 3, but not for release builds where the too-large defaults were used.
Comment on attachment 8345201 [details] [diff] [review]
[buildbot-configs] Remove overrides from configs

I missed releasetestUptake settings in 
so I removed those at checkin too.
Attachment #8345201 - Flags: checked-in+
In production
All done here?
Whiteboard: [kanban:engops:]
Closed: 5 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.