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

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

315 bytes added , 18 July 2014

canmove, Confirmed users

6,441

edits

@@ Line 163: / Line 163: @@
 = Publish in Balrog =
-To publish a release in Balrog you need to change the "Mapping" for the appropriate rule. This can be done on [https://aus4-admin.mozilla.org/rules.html Balrog's rules page]. Each rule is associated with a Product and Channel.
+We have a builder that updates the right parts of Balrog to push a release live. When instructed, you can use "force build" to start it.
+Example buildbot URLs for the builder:
+* Beta (when QA signs off and requests the push):
+** [http://buildbot-master70.srv.releng.use1.mozilla.com:8001/builders/release-mozilla-beta-update_shipping Firefox Beta]
+** [http://buildbot-master70.srv.releng.use1.mozilla.com:8001/builders/release-comm-beta-update_shipping Thunderbird Beta]
+''Note that the master you force this on, is not necessarily the master that takes the job, watch your e-mail for completion status''
-For example, Firefox Beta releases have a Product of "Firefox" and Channel of "beta". To push build2 of 31.0b2, find the aforementioned rule, change it's Mapping to "Firefox-31.0b2-build2", and then click "Update" on the far right.
+In order to guard against accidents, this builder aborts unless a special property is set. You must enter a "shipit" property on the form, whose value is also "shipit".
 = Throttling =