Release:Release Automation on Mercurial:Documentation: Difference between revisions

Release:Release Automation on Mercurial:Documentation (view source)

Revision as of 18:32, 19 November 2010

533 bytes added , 19 November 2010

→‎Update/snippet Generation

Bhearsum

canmove, Confirmed users

6,441

edits

@@ Line 338: / Line 338: @@
 === Update/snippet Generation ===
+Code used:
+* 'ReleaseUpdatesFactory from [http://hg.mozilla.org/build/buildbotcustom/file/tip/process/factory.py process/factory.py]
+* [http://mxr.mozilla.org/mozilla/source/tools/patcher/patcher2.pl patcher2.pl and associated libraries]
+* [http://hg.mozilla.org/build/tools/file/tip/release/patcher-config-bump.pl patcher-config-bump.pl]
+* [http://hg.mozilla.org/build/tools/file/tip/release/update-verify-bump.pl update-verify-bump.pl]
+* [http://hg.mozilla.org/build/tools/file/tip/release/generate-candidate-build-updates.py generate-candidate-build-updates.py]
+* [http://hg.mozilla.org/build/tools/file/tip/release/compare-channel-snippets.sh compare-channel-snippets.sh]
 Deliverables:
 * Updated patcher config file, checked into CVS
@@ Line 343: / Line 351: @@
 * Update snippets on test & live channels
 * Snippet comparison log
-For those familiar with Bootstrap's Updates step this step is pretty much exactly the same.
 After checking out the necessary modules and tools this builder goes to work doing the following:
@@ Line 358: / Line 364: @@
 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.
-This step takes approximately 1 hour to complete.
 ==== Snippet Comparison Log Analysis ====