Account confirmers, Anti-spam team, canmove, Confirmed users, Bureaucrats and Sysops emeriti
4,083
edits
SeaMonkey:Release Process: Difference between revisions
Jump to navigation
Jump to search
→Creating Builds
| Line 71: | Line 71: | ||
As a first step, tinder-config.pl on all of those boxes must be corrected to pull the correct release tag and upload to directories with correct version numbers. | As a first step, tinder-config.pl on all of those boxes must be corrected to pull the correct release tag and upload to directories with correct version numbers. | ||
After logging into those boxes and doing this edit, I cd to the release-seamonkey-1.1 directory and execute "./tinderbox clobber restart" there, which does a BuildOnce clobber run producing the builds. Note that only Linux can do this from the remote ssh shell, Mac is done via VNC from a terminal window and Windows via RDP from a cmd window, so all of them can perform basic tinderbox tests on the builds. | After logging into those boxes and doing this edit, I cd to the release-seamonkey-1.1 directory and execute "./tinderbox clobber restart" there, which does a BuildOnce clobber run producing the builds (for a respin on the same day as a previous one, the <code>last-built</code> files need to be deleted!). Note that only Linux can do this from the remote ssh shell, Mac is done via VNC from a terminal window and Windows via RDP from a cmd window, so all of them can perform basic tinderbox tests on the builds. | ||
The Linux machine has additional stuff added to produce source tarballs. I have a script there that does | The Linux machine has additional stuff added to produce source tarballs. I have a script there that does | ||