Closed Bug 632845 Opened 9 years ago Closed 9 years ago

Bouncer submitter should be triggered just after tagging

Categories

(Release Engineering :: General, defect, P2)

defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: armenzg, Assigned: rail)

References

Details

Attachments

(2 files)

Instead of having to trigger it manually.

Could we please also add the EUBallot at the same time?
Assignee: nobody → rail
Priority: P4 → P2
Attached patch toolsSplinter Review
* Added win32-EUballot platform template and bouncer_platform_map entry
* Added --bouncer-product-suffix parameter
Attachment #511414 - Flags: review?(bhearsum)
Attached patch buildbotcustomSplinter Review
added schedulers for build1 only (EUballot only if releaseConfig['doPartnerRepacks'] is set)
Attachment #511415 - Flags: review?(bhearsum)
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.
Attachment #511415 - Flags: review?(bhearsum) → review+
Attachment #511414 - Flags: review?(bhearsum) → review+
Closing w/o landing it, because the next release cycle implies deploy+reconfig.
Status: NEW → RESOLVED
Closed: 9 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.