Calendar:Release Build Instructions: Difference between revisions

Calendar:Release Build Instructions (view source)

1,242 bytes added , 3 January 2012

canmove, Confirmed users, Bureaucrats and Sysops emeriti

3,628

edits

@@ Line 16: / Line 16: @@
 == Starting the builds ==
-*
+* Clobber the calendar release builders (currently: 'tag', 'source', 'win32_build', 'macosx64_build', 'linux64_build', 'linux_build').
+* ssh into the Calendar buildbot master
+* Pull the latest configs and reconfigure the master:
+ $ cd calendar/buildbot-configs
+ $ # Check diffs
+ $ hg diff
+ $ # Check which revision you're on currently
+ $ hg identify
+ $ # Do the update
+ $ hg pull -u
+ $ # Check config
+ $ cd /buildbot/calendar
+ $ ./buildbot.sh checkconfig master.cfg
+ $ # and reconfig
+ $ ./buildbot.sh reconfig
+* If you see "Reconfiguration appears to have completed successfully." then continue, else wait 5 minutes and then continue.
+* Kick off the build, noting:
+** Branch should be releases/comm-beta or releases/comm-release as appropriate
+** The message in -m should be unique, otherwise buildbot may get confused.
+ $ ./buildbot.sh sendchange --username=<who you are> --master=localhost:9030 --branch=releases/comm-release -m "Lightning 1.1 final build 1 kick 1" doit
+* At this stage, the master should show that the "tag" builder either has a build pending, or is running.
+* 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.