502992 - Have release-automation (Fx3.0/1.9.0) send notifications to release@m.c

Status: RESOLVED FIXED

(Release Engineering :: General, defect)

Description

[John O'Duinn [:joduinn] (please use "needinfo?" flag)]

The release-automation for FF3.0.x sends status emails (step completion, etc) to build@m.o. However, we are all on release@m.c, so emails should go there instead.

Please change automation to use release@m.c, in preparation for moving any remaining community folks on build@m.o over to community-build@m.o.

Comment 1

[Armen [:armenzg]]

Attachment: send emails to release@m.c for 1.9.0 releases

Here is the list of files where build@m.o is being used in case we want to make more changes:
./buildbot-configs/automation/staging/master.cfg
./buildbot-configs/automation/staging/tb-master.cfg
./release/configs/fx-moz18-bootstrap.cfg
./release/configs/fx-moz180-bootstrap.cfg
./release/configs/fx-moz19-bootstrap.cfg
./release/configs/tb-moz18-bootstrap.cfg
./release/configs/tb-moz180-bootstrap.cfg
./release/configs/xr-moz19-bootstrap.cfg
./tinderbox-configs/firefox/linux/tinder-config.pl
./tinderbox-configs/firefox/macosx/tinder-config.pl
./tinderbox-configs/firefox/win32/tinder-config.pl
./tinderbox-configs/seamonkey/linux/tinder-config.pl
./tinderbox-configs/sunbird/macosx/tinder-config.pl
./tinderbox-configs/thunderbird/macosx/tinder-config.pl
./tinderbox-configs/xulrunner/win32/tinder-config.pl

Comment 2

[[e-mail] (:bhearsum)]

Don't forget to check the release and l10n_release branches for all of those tinder-config.pl files - they're the ones that are used for Firefox 3.0.x releases.

Comment 3

[Armen [:armenzg]]

I checked the branches l10n, release and release_l10n and the email is only being used for thunderbird and xulrunner

Comment 4

[Nick Thomas [:nthomas] (UTC+12)]

From what I can tell from the tinderbox code, $BuildAdministrator only appears in logs and doesn't cause any actual mail. So I wouldn't be worried about modifying all the tinderbox configs. (There are many more instances than you found, because in some places we use "build\@mozilla.org"). We could ignore the old bootstrap configs too, and just change
  release/configs/tb-moz18-bootstrap.cfg
  release/configs/fx-moz19-bootstrap.cfg
  release/configs/xr-moz19-bootstrap.cfg

Comment 5

[Armen [:armenzg]]

Putting it into the queue since I won't be touching it anytime before 2 weeks.

Comment 7

[Nick Thomas [:nthomas] (UTC+12)]

Attachment: Update all bootstrap configs

I'll take a look at the blat config for the windows boxes too.

Comment 8

[Nick Thomas [:nthomas] (UTC+12)]

(In reply to comment #7)
> I'll take a look at the blat config for the windows boxes too.

This is a red herring.

Comment 9

[Nick Thomas [:nthomas] (UTC+12)]

Comment on attachment 421689 [details] [diff] [review]
Update all bootstrap configs

If this gets spammy then main person driving the release can be in 'to' and  set cc to joduinn to keep him in the loop.