258
edits
Calendar:Release Build Instructions: Difference between revisions
no edit summary
No edit summary |
|||
| Line 7: | Line 7: | ||
== Preparing for the builds == | == Preparing for the builds == | ||
=== l10n === | === l10n === | ||
* Someone needs to hit the ship-it button on the [https://l10n | * Someone needs to hit the ship-it button on the [https://l10n.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]. | * 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]. | ||
=== comm-beta/comm-release === | |||
* Update calendar/locales/shipped-locales from the l10n dashboard, make sure to remove en-US from the list. | |||
* Modify calendar/lightning/install.rdf to use fixed min/maxVersions for Seamonkey and Thunderbird | |||
* Push everything to comm-beta or comm-release. Remember this changeset for the following section. | |||
=== buildbot-configs repository === | === buildbot-configs repository === | ||
| Line 19: | Line 24: | ||
* Push everything to buildbot-configs. | * Push everything to buildbot-configs. | ||
== Starting the builds == | == Starting the builds == | ||
| Line 31: | Line 31: | ||
* Pull the latest configs and reconfigure the master: | * Pull the latest configs and reconfigure the master: | ||
$ cd /buildbot/calendar | $ cd /buildbot/calendar | ||
$ ./ | $ ./update.sh | ||
* 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. | ||
| Line 52: | Line 42: | ||
$ ./release.sh release 1.3 | $ ./release.sh release 1.3 | ||
* At this stage, the [https:// | * At this stage, the [https://calendar-master.mozillalabs.com/builders/tag/ master should show] that the "tag" builder either has a build pending, or is running. | ||
* If the tag build is pending, you might want to stop it using the [https:// | * If the tag build is pending, you might want to stop it using the [https://calendar-master.mozillalabs.com/buildslaves/momo-vm-cal-linux-01 buildbot web interface] | ||
* It is a good idea to check the comm-* and mozilla-* repositories during/after tagging to ensure the correct thing has been tagged and version bump is correct. | * It is a good idea to check the comm-* and mozilla-* repositories during/after tagging to ensure the correct thing has been tagged and version bump is correct. Also, stick around for the first 2 minutes of the platform builds in case they error out. | ||
== Post Build Step == | == Post Build Step == | ||
* ssh into | * ssh into stage.mozilla.org and run the following to unify the Linux builds (currently run in the home directory, should really move to be running on buildbot, there's a bug on that somewhere): | ||
$ # <version> is the version number e.g. 1.1, <build> is the build number e.g. 1. | $ # <version> is the version number e.g. 1.1, <build> is the build number e.g. 1. | ||
$ sh fix_linux_xpi.sh <version> <build> | $ sh fix_linux_xpi.sh <version> <build> | ||