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

Jump to navigation Jump to search

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

Revision as of 17:33, 16 August 2012

1,738 bytes removed ,  16 August 2012
→‎Others
(Moved beta->release merge steps to https://wiki.mozilla.org/Release_Management/Merge_Documentation#Beta-.3ERelease_Merge)
Line 70: Line 70:
| l10nChunks
| l10nChunks
| The number of l10n builders to be used, per platform. If not present, defaults to DEFAULT_PARALLELIZATION set in [http://hg.mozilla.org/build/buildbotcustom/file/tip/process/release.py process/release.py].
| The number of l10n builders to be used, per platform. If not present, defaults to DEFAULT_PARALLELIZATION set in [http://hg.mozilla.org/build/buildbotcustom/file/tip/process/release.py process/release.py].
|-
| cvsroot
| The cvsroot to use for pulling MozBuild, patcher tools, and other things from CVS. It is also used to check in an update patcher config file and as such must be an account with write access.
|-
|-
| productName
| productName
Line 79: Line 76:
| appName
| appName
| The lowercase application name. Eg, 'browser', 'mailnews', etc.
| The lowercase application name. Eg, 'browser', 'mailnews', etc.
|-
| binaryName
| The name which will be used in the filenames of installers, packages, and MARs. Usually is the same as productName.
|-
| oldBinaryName
| Same as above, but for the oldVersion.
|-
|-
| version/appVersion
| version/appVersion
Line 100: Line 91:
| baseTag
| baseTag
| The base tag to use when tagging repositories. _BUILD$buildNumber and _RELEASE will be appending to this where necessary.
| The base tag to use when tagging repositories. _BUILD$buildNumber and _RELEASE will be appending to this where necessary.
|-
| oldVersion/oldAppVersion
| Same thing as version/appVersion, but applies to the previous release. When 3.1rc1 is shipped oldVersion and oldAppVersion will both be 3.1b3. When we ship 3.1.1 oldVersion will be, eg, 3.1rc2 and oldAppVersion will be 3.1.
|-
| oldBuildNumber
| The build number of the previous release. This should be the build number which was actually shipped.
|-
| oldBaseTag
| Same as baseTag, but for the previous release.
|-
|-
| enUSPlatforms
| enUSPlatforms
Line 160: Line 142:
| updateVerifyChunks
| updateVerifyChunks
| The number of builders to be used for update verify, per platform. If not present, defaults to DEFAULT_PARALLELIZATION set in [http://hg.mozilla.org/build/buildbotcustom/file/tip/process/release.py process/release.py].
| The number of builders to be used for update verify, per platform. If not present, defaults to DEFAULT_PARALLELIZATION set in [http://hg.mozilla.org/build/buildbotcustom/file/tip/process/release.py process/release.py].
|-
| majorUpdateRepoPath
| The relative path repository that contains the shipped-locales file for the major update "to" release. If None, the rest of the majorUpdate* variables are not necessary.
|-
| majorUpdateToVersion, majorUpdateAppVersion, majorUpdateBuildNumber, majorUpdateBaseTag
| These variables contain information about the release you are generating a major update to. See version/appVersion/buildNumber/baseTag for descriptions of them.
|-
| majorUpdateReleaseNotesUrl
| Major Update release notes URL. If None use the default URL. Introduced in {{bug|553059}}.
|-
| majorUpdatePatcherConfig
| The Patcher config file to use for the major update. This can be an existing file, in which case it will be overwritten and committed, or a non-existant file, in which case it will be created and committed.
|-
| majorUpdateVerifyConfigs
| See updateVerifyConfigs description above.
|-
|-
| testOlderPartials
| testOlderPartials
Bhearsum
canmove, Confirmed users
6,441

edits

Retrieved from "https://wiki.mozilla.org/Special:MobileDiff/461666"

Navigation menu