ReleaseEngineering/How To/Generate partial updates: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(Created page with "__TOC__ {{Release Engineering How To|Generate_partial_updates}} = Intro = This document is about generating partial updates from older releases, eg N-2 to N, on request from Rel...")
 
No edit summary
Line 7: Line 7:
Assumptions:
Assumptions:
* The automated updates builder has already run, and you're re-using the slave for the copy of the utilities and scripts you need
* The automated updates builder has already run, and you're re-using the slave for the copy of the utilities and scripts you need
* the request is for the release channel
= Config files =
== Patcher config ==
To get setup
* Grab a copy of the release config, mozRelease-branch-patcher2.cfg, from your own CVS checkout or from [http://mxr.mozilla.org/mozilla/source/tools/patcher-configs/mozRelease-branch-patcher2.cfg?raw=1 mxr]
* Rename it to mozRelease-branch-patcher2-XXXXXX.cfg, where XXXXXX is the bug number for the request
* Verify that the file is up to date by checking the values of <tt>from</tt> and <tt>to</tt> in <tt><current-update></tt>, and the right buildN in the <tt>completemarurl</tt> of the <tt><releases></tt> block for the release being created
To modify the config
* in the <tt><current-update></tt> block
** change the <tt>from</tt> version
** in the <tt><partial></tt> block change the from version in the paths
* remove all the past-update lines just below <tt><current-update></tt> block
* remove the unneeded blocks from <tt><release></tt>
* if only some platforms are needed (eg windows), remove the other platforms from the <tt><platforms></tt> blocks
Attach the file to the bug.

Revision as of 02:56, 12 July 2012

Intro

This document is about generating partial updates from older releases, eg N-2 to N, on request from Release Management. We generate N-1 to N updates in the release automation, but more than that is a manual process until bug 575317 makes some progress.

Assumptions:

  • The automated updates builder has already run, and you're re-using the slave for the copy of the utilities and scripts you need
  • the request is for the release channel

Config files

Patcher config

To get setup

  • Grab a copy of the release config, mozRelease-branch-patcher2.cfg, from your own CVS checkout or from mxr
  • Rename it to mozRelease-branch-patcher2-XXXXXX.cfg, where XXXXXX is the bug number for the request
  • Verify that the file is up to date by checking the values of from and to in <current-update>, and the right buildN in the completemarurl of the <releases> block for the release being created

To modify the config

  • in the <current-update> block
    • change the from version
    • in the <partial> block change the from version in the paths
  • remove all the past-update lines just below <current-update> block
  • remove the unneeded blocks from <release>
  • if only some platforms are needed (eg windows), remove the other platforms from the <platforms> blocks

Attach the file to the bug.