258
edits
Calendar:Release Build Instructions: Difference between revisions
Calendar:Release Build Instructions (view source)
Revision as of 15:08, 3 February 2012
, 3 February 2012no edit summary
No edit summary |
|||
| Line 6: | Line 6: | ||
== Preparing for the builds == | == Preparing for the builds == | ||
=== l10n === | |||
* Someone needs to hit the ship-it button on the [https://l10n-stage-sj.mozilla.org/shipping/milestones dashboard for the milestone]. | |||
* You won't have to file a bug anymore to create a new l10n milestone, but if you don't have a milestone to ship, then you can [https://bugzilla.mozilla.org/enter_bug.cgi?product=Mozilla%20Localizations&component=Infrastructure&short_desc=Please%20create%20a%20milestone%20for%20NNN&comment=I%20would%20appreciate%20if%20you%20could%20create%20a%20new%20milestone%20for%20Lightning%20NNN.%20Thanks%20in%20advance! file a bug]. | |||
* | === buildbot-configs repository === | ||
* | * Land the [http://hg.mozilla.org/build/buildbot-configs/file/default/calendar/l10n-calendar-changesets l10n changesets]. | ||
* You need to update [http://hg.mozilla.org/build/buildbot-configs/file/default/calendar/release_calendar.py release_calendar.py] with all information mentioned in the first section | |||
** | ** branchSuffix = 'release' or 'beta' | ||
** version | ** sourceRepoRevision, mozillaRepoVersion | ||
** The oldVersion | ** version, milestone (= gecko version), buildNumber | ||
* | ** The oldVersion, oldBuildNumber are usually updated, but it isn't vital in the current configuration. | ||
* Push everything to buildbot-configs. | |||
=== comm-beta/comm-release === | |||
* Update calendar/locales/shipped-locales from the l10n dashboard, make sure to remove en-US from the list. | |||
* Make sure calendar/sunbird/config/version.txt has the right value | |||
* Modify calendar/lightning/install.rdf to use fixed min/maxVersions for Seamonkey and Thunderbird | |||
* Push everything to comm-beta or comm-release. | |||
== Starting the builds == | == Starting the builds == | ||
| Line 35: | Line 45: | ||
* If you see "Reconfiguration appears to have completed successfully." then continue, else wait 5 minutes and then continue. | * If you see "Reconfiguration appears to have completed successfully." then continue, else wait 5 minutes and then continue. | ||
* Kick off the build | * Kick off the build using release.sh: | ||
$ ./ | $ # Usage: release.sh <beta|release> <version> [<buildnr>] [<kicknr>] | ||
$ ./release.sh beta 1.3b1 | |||
$ # or: | |||
$ ./release.sh release 1.3 | |||
* At this stage, the [https://buildbot-admin.mozillamessaging.com/calendar/builders/tag/ master should show] that the "tag" builder either has a build pending, or is running. | * At this stage, the [https://buildbot-admin.mozillamessaging.com/calendar/builders/tag/ master should show] that the "tag" builder either has a build pending, or is running. | ||
| Line 69: | Line 80: | ||
** Check if all that fails is the hg out step. If so, then the push step could have worked and tagging is correct. Use to force build button on the release and source builders (linux_build, linux64_build, win32_build, macosx64_build, source) | ** Check if all that fails is the hg out step. If so, then the push step could have worked and tagging is correct. Use to force build button on the release and source builders (linux_build, linux64_build, win32_build, macosx64_build, source) | ||
** If tagging partially failed, modify l10n-calendar-changesets to only include locales that weren't tagged and restart the tag builder. | ** If tagging partially failed, modify l10n-calendar-changesets to only include locales that weren't tagged and restart the tag builder. | ||
* ''' A platform builder fails (win32_build, linux_build, ...) | |||
** Just hit the 'restart build' button on the failed build. The build properties will be used from the failed build, so you don't have to reconfigure anything | |||
** You may even clobber a builder inbetween and then restart build. This won't disrupt anything. | |||