For the last releases (48.0, 49.0b1, 45.3.0esr) I miss the go to build emails to the release-drivers list. This can be somewhat confusing like as of today when there are nearly three identical builds available, only because of rebuilds due to automation failures. Finding what actually has to be tested on is hard. Lets make sure we get those emails send out again.

This looks like a pretty simple change to make in puppet at https://dxr.mozilla.org/build-central/source/puppet/manifests/moco-config.pp#196 Context here is bug 1136206, which I think ended up dropping the emails like [release] Firefox 35.0.1 build1: linux64 en-US build available and updates available from r-d, leaving just the build announcement emails going to the wider audience. Then we lost that in the switch to release promotion.

Of course it's not that simple. In tools/buildfarm/release/release-runner.sh we grep for 'notify_to:' so that we can send errors to a !r-d address. So this adds a new config parameter for r-d, so we can just send announcements of new builds. Old release runner builds should keep working via this function https://hg.mozilla.org/build/tools/file/old-release-runner/buildfarm/release/release-runner.py#l240 that uses the release configs.

Only intended for default, not old-release-runner.

Comment on attachment 8781763 [details] [diff] [review] [puppet] Add new parameter for r-d address https://hg.mozilla.org/build/puppet/rev/9827e9134b05 https://hg.mozilla.org/build/puppet/rev/063ddddaa1ce

Comment on attachment 8781764 [details] [diff] [review] [tools] Use new config when calling email_release_drivers() https://hg.mozilla.org/build/tools/rev/4ce66dfaaeb2

Updated bm85:/builds/releaserunner/tools from f88596509502 to 4ce66dfaaeb2, and restarted runner. Leaving open for verification with the next Firefox desktop release - missed 48.0.1 build2 so probably 49.0b5.

Worked for 48.0.1 build3.