632845 - Bouncer submitter should be triggered just after tagging

Status: RESOLVED FIXED

(Release Engineering :: General, defect, P2)

Description

[Armen [:armenzg]]

Instead of having to trigger it manually.

Could we please also add the EUBallot at the same time?

Comment 1

[Rail Aliiev [:rail]]

Attachment: tools

* Added win32-EUballot platform template and bouncer_platform_map entry
* Added --bouncer-product-suffix parameter

Comment 2

[Rail Aliiev [:rail]]

Attachment: buildbotcustom

added schedulers for build1 only (EUballot only if releaseConfig['doPartnerRepacks'] is set)

Comment 3

[Rail Aliiev [:rail]]

BTW, an example command for EUballot is:

python tuxedo-add.py --config firefox-tuxedo.ini --product firefox --version 3.6.15 --tuxedo-server-url https://tuxedo.stage.mozilla.com/api/ --bouncer-product-name Firefox --brand-name Firefox --milestone 1.9.2.15 --bouncer-product-suffix EUballot --platform win32-EUballot --credentials-file BuildSlaves.py

stdio output is:

Adding product: Firefox-3.6.15-EUballot
Server response:
<?xml version="1.0" encoding="utf-8"?><products><product id="745" name="Firefox-3.6.15-EUballot"/></products>
Adding location for Firefox-3.6.15-EUballot, win: /firefox/releases/3.6.15/win32-EUballot/:lang/Firefox%20Setup%203.6.15.exe

I checked staging Bouncer server, the entry was added.

Comment 4

[Rail Aliiev [:rail]]

Comment on attachment 511414 [details] [diff] [review]
tools

http://hg.mozilla.org/build/tools/rev/75d7855dd05e

Comment 5

[Rail Aliiev [:rail]]

Comment on attachment 511415 [details] [diff] [review]
buildbotcustom

http://hg.mozilla.org/build/buildbotcustom/rev/cd7e22d28d84

Comment 6

[Rail Aliiev [:rail]]

Closing w/o landing it, because the next release cycle implies deploy+reconfig.