Deliverables:
* Updated patcher config file
* Update snippets on test & live channelsUpdated update verify configs* Release blobs submitted to production Balrog* Snippet comparison logUpdated test channel rules in Balrog, pointing at the new release Blob
After checking out the necessary modules and tools this builder goes to work doing the following:
* Bumping & checking in a patcher config file
* Creating & uploading update snippets
* When applicable, creating snippets for previous builds of the release
* Pushing test snippets live
* When applicable, doing a comparison of live channel snippets vs. releasetest
This step is generally pretty failsafe but in the event that it needs to be run a second time or restarted at later step it's necessary to comment out the patcher config bump step (see [[#Restarting_a_builder_from_a_certain_point | below]] for details on how). Until <strike>{{bug|466999}} FIXED</strike> is resolved the patcher config file can only be bumped once.
Note that both the sourceRepo and the tools repo will be updated to the patcherToolsTag. If the update-packaging tools or patcher config script has been updated since the last release it is a good idea (and sometimes necessary) to create a new UPDATE_PACKAGING_R# tag before starting the release. [[ReleaseEngineering/PatcherTags]] documents the tag history, please keep it up to date.
= Set-up whatsnew page =
= Bouncer Submitter =
Code:* 'TuxedoEntrySubmitterFactory' from [http:This builder is triggered automatically after tagging completes, and creates and//hg.mozilla.org/build/buildbotcustom/file/tip/process/factory.py process/factory.py]* [http://hg.mozilla.org/build/tools/file/tip/release/tuxedoor updates bouncer entries used on -add.py tuxedo-add.py]Configuration:* [http://hg.mozilla.org/build/tools/file/tip/release/firefox-tuxedo.ini firefox-tuxedo.ini] for stable versionscdntest and live update channels, and [http://hg.mozilla.org/build/tools/file/tip/release/firefox-devpreview-tuxedo.ini firefox-devpreview-tuxedo.ini] for Alpha releases.* BuildSlaves.py file should contain the following variables:** tuxedoUsername: Tuxedo username with appropriate permissions for adding new bouncer entries via API** tuxedoPassword: password for this user This builder can be started any time with 'Force Build' from the Buildbot waterfallthat Bedrock points at.
This step adds adds bouncer entries for installers, complete and partial updates for all platforms listed in enUSPlatforms and l10nPlatforms and locales specified in shipped-locales (en-US is being added in any case).
