SeaMonkey:Release Process:2.3.3: Difference between revisions

no edit summary
(Created page with "{{RTOC}} <small>« SeaMonkey 2.3.3</small> == Build Harness == SeaMonkey:Release Automation == Bugs == Tracking bug filed as {{bug|683719}...")
 
No edit summary
Line 10: Line 10:
== Build Engineer ==
== Build Engineer ==
Justin Wood
Justin Wood
== WE ARE HERE ==


== Signed-off Revisions ==
== Signed-off Revisions ==
{{hg|e474d3d6b63e|releases/comm-release|;releases/comm-release
{{hg|311f330a36a6|releases/comm-release|;releases/comm-release
:}}
:}}
{{hg|6176fcd0daf8|releases/mozilla-release|;releases/mozilla-release
{{hg|7a4871571868|releases/mozilla-release|;releases/mozilla-release
:}}<br><small>(SEAMONKEY_2_3_RELBRANCH)</small>
:}}<br><small>(SEAMONKEY_2_3_3_RELBRANCH)</small>
{{hg|DOMI_2_0_10_RELEASE|dom-inspector|;dom-inspector
{{hg|DOMI_2_0_10_RELEASE|dom-inspector|;dom-inspector
:}}<br><small>(DOMI_2_0_10)</small>
:}}<br><small>(DOMI_2_0_10)</small>
Line 30: Line 28:
* Have to do the same s/mac/mac64/ work as in SeaMonkey 2.1b2. Will have to look into an easier way for that
* Have to do the same s/mac/mac64/ work as in SeaMonkey 2.1b2. Will have to look into an easier way for that
* Enabled the version bumping for this release, as we'll be 2.3.3
* Enabled the version bumping for this release, as we'll be 2.3.3
* Re-Relbranched on m-release, to save confusion.


=== Build ===
=== Build ===
Line 38: Line 37:
* Kicked off with the following command:
* Kicked off with the following command:
  buildbot sendchange --username=Callek --master=localhost:9010 --branch=releases/comm-release -c "SeaMonkey 2.3.1build1" doit
  buildbot sendchange --username=Callek --master=localhost:9010 --branch=releases/comm-release -c "SeaMonkey 2.3.1build1" doit
* Tagging ('''Run 1''') failed due to COMM* relbranch already existing, TB tagged same day, updated configs and kicked again.
* Tagging completed fine
* Tagging ('''Run 2'''), due to version bump for SeaMonkey already existing. Removed version from config file, kicked again.
* Linux64 failed with the config clone, retriggered, and that finished fine.
* Tagging ('''Run 3''') failed due to not removing previous release runs, ran relclean.sh and ran again
* All repacks finished fine.
* Tagging ('''Run 4''') failed due to run 2 completing the branching for cZ (and inspector) already. Updated config to comment out cZ/inspector repo's from the "to tag" stuff.
* Tagging ('''Run 5''') succeeded.
* Mac OSX64 Build failed due to builder not checking out inspector/cZ due to tagging removal above, but mozconfig still having it.
** Canceled all pending builds, and stopped '''source''' creation, updated configs again, and kicked with a dummy tag factory.
* Noticed that since the version bump failed in Tagging Run 2, I never actually updated the rev-to-tag for comm-release, so manually moved our tag (but accidentally created the tag on default not the relbranch -- this is ok). Also noticed that I did not clobber since that mac64 fail, so killed all pending jobs (linux build, linux source, mac build) ran relclean.sh and then kicked again with dummy tag factory.
* Builds completed fine
* Repacks, had linux nb-NO fail due to a (temp) upload failure. Manually re-ran through web interface, and setting our three properties via that.


=== Fake tr locale ===
=== Fake tr locale ===
Line 59: Line 51:
* We have no signing infrastructure for SeaMonkey right now, so I faked the signing step that is usually done after completion of builds and L10n repacks and before the update generation.
* We have no signing infrastructure for SeaMonkey right now, so I faked the signing step that is usually done after completion of builds and L10n repacks and before the update generation.
* Logged onto stage-old.mozilla.org and ran <code>sh ~/fakesign.sh</code>
* Logged onto stage-old.mozilla.org and ran <code>sh ~/fakesign.sh</code>
== WE ARE HERE ==


=== Updates and Verification ===
=== Updates and Verification ===
Account confirmers, Anti-spam team, Confirmed users, Bureaucrats and Sysops emeriti
1,529

edits