Release:Release Automation on Mercurial:Updates through Shipping: Difference between revisions

← Older edit

Release:Release Automation on Mercurial:Updates through Shipping (view source)

Revision as of 16:59, 11 December 2017

888 bytes removed , 11 December 2017

bm70 was decomm'd

Callek

Account confirmers, Anti-spam team, Confirmed users, Bureaucrats and Sysops emeriti

1,529

edits

@@ Line 100: / Line 100: @@
 = Push to mirrors =
-**only applicable for non release promotion releases**
+'''''only applicable for non release promotion releases'''''
 For GA release builds, this step is not run automatically, and must be manually triggered (below) after receiving the go from RelMgmt. For all other releases, this step is run automatically.
-Code: [http://hg.mozilla.org/build/tools/file/tip/scripts/release/stage-tasks.py scripts/release/stage-tasks.py]
 * Release
-** [http://buildbot-master70.bb.releng.use1.mozilla.com:8001/builders/release-mozilla-release-fennec_push_to_mirrors Fennec Release]
+** [http://buildbot-master71.bb.releng.use1.mozilla.com:8001/builders/release-comm-esr52-thunderbird_push_to_mirrors Thunderbird 52 Release]
-*** prerequisites: wait for driver email subj like '(Android|fennec|mobile firefox) $version $buildnum (uploaded|pushed|published) to (Google Play|play store)'
-*** Note: push to mirrors step can happen after we push to play store, since we serve updates through google play and not balrog (so cdn/mirrors don't need apks).
-** [http://buildbot-master70.bb.releng.use1.mozilla.com:8001/builders/release-comm-esr38-thunderbird_push_to_mirrors Thunderbird 38 Release]
-** [http://buildbot-master70.bb.releng.use1.mozilla.com:8001/builders/release-comm-esr45-thunderbird_push_to_mirrors Thunderbird 45 Release]
-** [http://buildbot-master70.bb.releng.use1.mozilla.com:8001/builders/release-comm-esr52-thunderbird_push_to_mirrors Thunderbird 52 Release]
 *** prerequisites: wait for driver email subj like 'push Thunderbird $version $buildnum to (release-cdntest channel|cdn|mirrors)'
-*** Note: antivirus and update_verify automation emails should be completed
+*** Note: update_verify automation emails should be completed
 This builder:
@@ Line 122: / Line 116: @@
 When enableAutomaticPushToMirrors is True, this is triggered automatically after the antivirus scan is done. When False, it must be manually triggered with Force Build. Step will automatically send email when complete.
+The code used to be in
+[http://hg.mozilla.org/build/tools/file/tip/scripts/release/stage-tasks.py scripts/release/stage-tasks.py] (for historical revisions) but is now a [https://dxr.mozilla.org/mozilla-central/source/testing/mozharness/scripts/release/push-candidate-to-releases.py?q=path%3Apush-candidate-to-releases.py&redirect_type=single mozharness] script
 = Final Verification =
@@ Line 154: / Line 151: @@
 = Publish in Balrog =
-**only applicable for non release promotion releases**
+'''''only applicable for non release promotion releases'''''
 == Betas/Final Releases ==
@@ Line 166: / Line 163: @@
 Example buildbot URLs for the builder:
-* [http://buildbot-master70.bb.releng.use1.mozilla.com:8001/builders/release-comm-beta-update_shipping_beta Thunderbird Beta]
+* [http://buildbot-master71.bb.releng.use1.mozilla.com:8001/builders/release-comm-beta-update_shipping_beta Thunderbird Beta]
-* [http://buildbot-master70.bb.releng.use1.mozilla.com:8001/builders/release-comm-esr45-update_shipping_release Thunderbird 45 Release]
+* [http://buildbot-master71.bb.releng.use1.mozilla.com:8001/builders/release-comm-esr52-update_shipping_release Thunderbird 52 Release]
-* [http://buildbot-master70.bb.releng.use1.mozilla.com:8001/builders/release-comm-esr52-update_shipping_release Thunderbird 52 Release]
@@ Line 216: / Line 212: @@
 = Post-release tasks =
-**only applicable for non release promotion releases**
+'''''only applicable for non release promotion releases'''''
-Releases are considered 'shipped' when
+Thunderbird is the only type of release that is non-release-promotion. After release is live, two more tasks need to be performed: marking them as shipped and run the BB post-release builder. They should be run at the same time, after release is live.
-* android - the apks have been uploaded to the Play Store
-The post-release tasks should be run immediately afterwards.
 == Mark as shipped on Ship It ==
@@ Line 230: / Line 224: @@
 Example buildbot URLs for the builder:
 * Beta
-** [http://buildbot-master82.build.mozilla.org:8001/builders/release-mozilla-beta-fennec_postrelease Fennec Beta]
 ** [http://buildbot-master82.build.mozilla.org:8001/builders/release-comm-beta-thunderbird_postrelease Thunderbird Beta]
 * Release
-** [http://buildbot-master82.build.mozilla.org:8001/builders/release-mozilla-release-fennec_postrelease Fennec Release]
-** [http://buildbot-master82.build.mozilla.org:8001/builders/release-comm-esr45-thunderbird_postrelease Thunderbird 45 Release]
 ** [http://buildbot-master82.build.mozilla.org:8001/builders/release-comm-esr52-thunderbird_postrelease Thunderbird 52 Release]
 ''Note that the master you force this on, is not necessarily the master that takes the job, watch your e-mail for completion status. Subject will be "[https://github.com/mozilla/build-buildbot-configs/blob/master/mozilla/release_templates/default_success %(releaseName)s: completed %(stage)s]".''