SeaMonkey:Release Automation: Difference between revisions

Line 44: Line 44:


SeaMonkey release automation tags all of the affected comm and Mozilla repos, inspector, venkman, and localizations on Mercurial as well as ChatZilla on CVS. For Chatzilla, no relbranch is created, we just do static tags at a given dated version from CVS trunk.
SeaMonkey release automation tags all of the affected comm and Mozilla repos, inspector, venkman, and localizations on Mercurial as well as ChatZilla on CVS. For Chatzilla, no relbranch is created, we just do static tags at a given dated version from CVS trunk.
=== Signing ===
We have no signing infrastructure for SeaMonkey right now, so we fake the signing step that is usually done after completion of builds and L10n repacks and before the update generation.
We log onto stage-old.mozilla.org and use those commands to do the following:
# seabld@stage-old
VERSION=2.0a4
BUILD=1
cd /home/ftp/pub/firefox/nightly/${VERSION}-candidates/build${BUILD}
mkdir win32 update/win32
rsync -av --exclude=*.zip unsigned/win32/ win32/
rsync -av unsigned/update/win32/ update/win32/
rsync -av unsigned/win32_info.txt .
echo "faked" > win32_signing_build${BUILD}.log
We purposely make copies here rather than symlinking for a couple of reasons: L10n verify scripts barf when they get zip files (hence the --exclude above), 'updates' factory will blow away complete MARs upon upload if update/win32 is a symlink. The echo creates the log the automation looks for, in order to continue to l10n verify and updates.
Account confirmers, Anti-spam team, canmove, Confirmed users, Bureaucrats and Sysops emeriti
4,083

edits