Changes between Version 9 and Version 10 of BuildClientProcedure
- Timestamp:
- Jul 31, 2007, 1:31:59 PM (17 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
BuildClientProcedure
v9 v10 6 6 = Client Build Procedure = 7 7 8 Note: All instructions assume you rbuilding on a Windows machine with TortoiseSVN installed.8 Note: All instructions assume you're building on a Windows machine with TortoiseSVN installed. 9 9 10 10 == Fork Tree == … … 12 12 If this is a major or minor version change to an even numbered minor revision you'll need to fork the tree. 13 13 14 {{{ 15 #!comment Should add instructions on how to make a branch with the command-line svn. 16 }}} 17 14 18 1. Right-click on the 'boinc' directory from trunk, and then select 'TortoiseSVN | Branch/Tag' 15 19 2. Change the "To URL:" to `http://boinc.berkeley.edu/svn/branches/boinc_core_release_<major>_<minor>`, where `<major>` is the major version number and `<minor>` is the minor version number. 16 3. Adjust version numbers in both the new branch and truck so that the new branch and trunk 17 reflect the current development efforts. 20 3. Adjust version numbers in both the new branch and truck so that the new branch and trunk reflect the current development efforts. 18 21 19 The branch should represent the new stable major and even minor version numbers. Trunk should represent the 20 next major and odd minor version number. 22 The branch should represent the new stable major and even minor version numbers. Trunk should represent the next major and odd minor version number. 21 23 22 24 The files that need to be modified are `configure.ac` and `version.h`. … … 37 39 2. Change the "To URL:" to `http://boinc.berkeley.edu/svn/branches/boinc_core_release_<major>_<minor>_<revision>` 38 40 39 Where <major> is the major version number, <minor> is the minor version number, and <revision>is the revision number.41 Where `<major>` is the major version number, `<minor>` is the minor version number, and `<revision>` is the revision number. 40 42 41 43 == Build Client == 42 44 43 Launch the boinc.slnproject file and build both the 'Win32' and 'x64' targets of the 'ReleaseSigned' built type.45 Launch the `boinc.sln` project file and build both the 'Win32' and 'x64' targets of the 'ReleaseSigned' built type. 44 46 45 47 == Sanity Test New Binaries == 46 48 47 Run the BOINC manager and attach to the BOINC alpha test project, let run for 15 min s. Traverse all the tabs, verify the status fields as a result traverses the crunching process.49 Run the BOINC manager and attach to the BOINC alpha test project, let run for 15 minutes. Traverse all the tabs, verify the status fields as a result traverses the crunching process. 48 50 49 51 == Code Sign Binaries == 50 52 51 The the `SignCode.cmd` file from the win_builddirectory. This batch file should be run from within a Visual Studio command shell. !SignCode should contain a series of the following line:53 Rum the [attachment:SignCode.cmd SignCode.cmd] file from the `win_build` directory. This batch file should be run from within a Visual Studio command shell. !SignCode should contain a series of the following line: 52 54 53 55 {{{ … … 65 67 == Build Setup Packages == 66 68 67 Launch BOINC.ism and BOINCx64.ism from the win_build/installerv2directory.69 Launch `BOINC.ism` and `BOINCx64.ism` from the `win_build/installerv2` directory. 68 70 69 71 With each file you'll need to change the following items before building the new setup package: 70 72 {{{ 73 1. Switch the the 'Installation Designer' tab. 74 2. Expand the 'Installation Information' node. 75 3. Click on the 'General Information' tree item. 76 4. Click on the 'Product Properties' from the 'General Information' secondary tree. 77 5. Update version number in the 'Version' field. 78 6. Update the product code GUID by highlighting it all and then clicking on the 'Generate GUID' button below. 79 7. Expand the 'Media' tree item. 80 8. Click on the 'Releases' tree item. 81 9. Click on the tree item below the 'Releases' secondary tree. 82 10. Update the file name with the correct version number. 71 83 72 1. Switch the the 'Installation Designer' tab. 73 2. Expand the 'Installation Information' node. 74 3. Click on the 'General Information' tree item. 75 4. Click on the 'Product Properties' from the 'General Information' secondary tree. 76 5. Update version number in the 'Version' field. 77 6. Update the product code GUID by highlighting it all and then clicking on the 'Generate GUID' 78 button below. 79 7. Expand the 'Media' tree item. 80 8. Click on the 'Releases' tree item. 81 9. Click on the tree item below the 'Releases' secondary tree. 82 10. Update the file name with the correct version number. 84 NOTE: If this is the first time you have built from the build tree you'll need to update the path variables in the 'Media' tree. Click on the 'Path Variables' tree item and update the `PATH_TO_BOINC_FILES`, `PATH_TO_LOCALE_FILES`, and `PATH_TO_RELEASE_FILES` environment variables. 83 85 86 11. Build Setup packages by selecting 'Build/Batch Build' from the menu. 84 87 }}} 85 88 86 NOTE: If this is the first time you have built from the build tree you'll need to update the87 path variables in the 'Media' tree. Click on the 'Path Variables' tree item and update the88 PATH_TO_BOINC_FILES, PATH_TO_LOCALE_FILES, and PATH_TO_RELEASE_FILES environment variables.89 90 89 {{{ 91 92 11. Build Setup packages by selecting 'Build/Batch Build' from the menu. 93 90 #!comment I'm leaving this list on a source block because I couldn't figure out how to do the NOTE, and keep the last item as '11'. 94 91 }}} 95 92 96 93 == Test Setup Package == 97 94 98 Copy the setup package from 'win_build/Installerv2/BOINC/Web32/Web/DiskImages/Disk1' to a 99 temporary location and execute the installer. Verify single user installation. 95 Copy the setup package from 'win_build/Installerv2/BOINC/Web32/Web/DiskImages/Disk1' to a temporary location and execute the installer. Verify single user installation. 100 96 101 97 == Deploy Setup Packages == 102 98 103 Use scp to upload the completed setup packages to boincadm@isaac.ssl.berkeley.edu:boinc/doc/dl/.99 Use scp to upload the completed setup packages to `boincadm@isaac.ssl.berkeley.edu:boinc/doc/dl/`. 104 100 105 101 == Deploy Symbol Files == 106 102 107 Copy the Win32 PDB files to c:\Src\symbolsand execute the following command:103 Copy the Win32 PDB files to `c:\Src\symbols` and execute the following command: 108 104 109 105 {{{ 110 111 symstore.exe add /l /f c:\src\symbols\*.pdb /s c:\src\symstore /compress /t "BOINC x86" 112 /v "5.10.17" /o /c "Application Release" 113 106 symstore.exe add /l /f c:\src\symbols\*.pdb /s c:\src\symstore /compress /t "BOINC x86" /v "5.10.17" /o /c "Application Release" 114 107 }}} 115 108 116 Copy the x64 PDB files to c:\Src\symbolsand execute the following command:109 Copy the x64 PDB files to `c:\Src\symbols` and execute the following command: 117 110 118 111 {{{ 119 120 symstore.exe add /l /f c:\src\symbols\*.pdb /s c:\src\symstore /compress /t "BOINC x64" 121 /v "5.10.17" /o /c "Application Release" 122 112 symstore.exe add /l /f c:\src\symbols\*.pdb /s c:\src\symstore /compress /t "BOINC x64" /v "5.10.17" /o /c "Application Release" 123 113 }}} 124 114 … … 126 116 127 117 {{{ 128 129 118 pscp.exe -r -C c:\src\symstore boincadm@isaac.ssl.berkeley.edu:boinc/doc/ 130 131 119 }}} 132 120 133 121 == Update Versions.inc in doc directory == 134 122 135 Update the versions.incfile in the doc directory to point to the new version.123 Update the `versions.inc` file in the doc directory to point to the new version. 136 124 137 125 == Update Tests.inc in boinc_alpha directory == 138 126 139 127 SSH into isaac and cd into 'boinc_alpha'. 140 Update the tests.incfile to include the new version for testing.128 Update the `tests.inc` file to include the new version for testing. 141 129 142 == Announce new version on boinc_alpha@ssl.berkeley.edu==130 == Announce new version on mailing list == 143 131 144 Send out the announcement email to boinc_alpha@ssl.berkeley.edu.132 Send out the announcement email to [mlist:boinc_alpha boinc_alpha@ssl.berkeley.edu].
