Closed Bug 802593 Opened 12 years ago Closed 12 years ago

ChangeNotifier mail broken in multimaster

Categories

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

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: bhearsum, Assigned: bhearsum)

Details

Attachments

(1 file)

      No description provided.
I think this is because the ChangeNotifier isn't present on the scheduler master, and that's where I started the release. Possible solutions:
* Start releases on a build master instead
* Put ChangeNotifier's on the scheduler master
Comment on attachment 672514 [details] [diff] [review]
include release ChangeNotifier's on scheduler masters

It looks good in case if we have only 1 scheduler master. In release.py we have 2 change notifiers, one for the initial sendchange and one for "android signing" triggered by UrlPoller.

If we have more than 1 scheduler master we may end up with multiple UrlPollers and as result multiple emails for the second one.

Since we are going to remove android notifier soon (once we sign it on demand), let's proceed with this.
Attachment #672514 - Flags: review?(rail) → review+
Attachment #672514 - Flags: checked-in+
Updating summary because this affects android signing mail too.
Summary: "tagging started" mail broken in multimaster → ChangeNotifier mail broken in multimaster
https://wiki.mozilla.org/ReleaseEngineering:Maintenance says that this is in production now.
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: