Changes between Version 16 and Version 17 of Local/VersionDeployment

Changes between Version 16 and Version 17 of Local/VersionDeployment

Please note that these Trac pages are no longer being updated. Wiki contents/documentation have moved to GitHub.

Changes between Version 16 and Version 17 of Local/VersionDeployment

Please note that these Trac pages are no longer being updated. Wiki contents/documentation have moved to GitHub.

Changes between Version 16 and Version 17 of Local/VersionDeployment

Show
Ignore:
Timestamp:
01/22/13 14:06:05 (6 years ago)
Author:
gpress
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Local/VersionDeployment

    v16 v17  
    22Explains how to go about deploying a new version of the code, which consists of two main steps: updating the files that the software updaters on each node check for updates, and replacing the base installers that are incorporated in new installations. 
    33 
    4 '''If you only want to make a release candidate build (or one that includes tests) available to the Custom Installer Builder, do not follow any of the steps on this page. Instead, see BaseInstallers and manually copy the created files to /var/www/dist on seattle.cs (but not seattlegeni.cs).''' 
     4'''If you only want to make a release candidate build (or one that includes tests) available to the Custom Installer Builder, do not follow any of the steps on this page. Instead, see BaseInstallers and manually copy the created files to /var/www/dist on seattle.cs (but not seattleclearinghouse.poly.edu).''' 
    55 
    66== Step by Step == 
    77 1. Make sure the [wiki:Local/ContinuousBuild continuous build] shows all tests passing (aside from any expected, non-critical failures such as new build machines not fully configured or flaky tests). 
    8  1. First, we push the release to the betabox testbed and make sure all is well there before pushing it on the main (seattlegeni) testbed. 
     8 1. First, we push the release to the betabox testbed and make sure all is well there before pushing it on the main (seattleclearinghouse) testbed. 
    99  1. Log in to betabox (betabox.cs.washington.edu) as a user who has sudo privileges. 
    1010  1. `cd /home/release` 
     
    2222    * If you `svn diff` these files, the output should look like [attachment:blackbox-version-push-svn-diff.txt these diffs]. 
    2323  1. Now, we actually deploy the new version. Still from the `/home/release` directory, do the following (these are separate actions, their order does not matter): 
    24     * To update the base installers used by seattlegeni on betabox, run the following: 
     24    * To update the base installers used by Seattle Clearinghouse on betabox, run the following: 
    2525      * `./rebuild_base_installers_for_seattlegeni.sh VERSION_HERE` 
    2626      * [attachment:blackbox-rebuild-base-installers-output.txt example output] 
     
    3737    * '''Important: At this point, all nodes will be updating to the new version.''' 
    3838    * Pushing the update to all existing nodes (through the SoftwareUpdater) is done by this update_and_build.py script, not the remaining steps. 
    39     * The remaining steps are only to make installers downloaded from SeattleGeni be the new version you are releasing. 
     39    * The remaining steps are only to make installers downloaded from Seattle Clearinghouse be the new version you are releasing. 
    4040  1. Navigate to the base installer directory (/var/www/dist as of January 2009). 
    41   1. scp the new files here (these will be the versioned files, e.g. seattle_linux0.1d.tgz, and the unversioned files, e.g. seattle_linux.tgz) over to /home/custominstallerbuilder/live/custominstallerbuilder/html/static/installers/base/ (this is where the custom installer builder resides) on the seattle geni server (seattlegeni.cs.washington.edu). 
     41  1. scp the new files here (these will be the versioned files, e.g. seattle_linux0.1d.tgz, and the unversioned files, e.g. seattle_linux.tgz) over to /home/custominstallerbuilder/live/custominstallerbuilder/html/static/installers/base/ (this is where the custom installer builder resides) on the seattle geni server (seattleclearinghouse.poly.edu). 
    4242  1. Remove any installers cached in /var/www/dist/geni/*_dist/.   You can do {{{rm -rf /var/www/dist/geni/*_dist/}}}.